>> If a transaction marks a tuple for update and later commits without

>> actually having updated the tuple, [...] can we simply
>> set the HEAP_XMAX_INVALID hint bit of the tuple?
>
>AFAICS this is a reasonable thing to do.

Thanks for the confirmation.  Here's a patch which also contains some
more noncritical changes to tqual.c:
 .  make code more readable by introducing local variables for xvac
 .  no longer two separate branches for aborted and crashed.
    The actions were the same in all cases.

Manfred Koizar

src/backend/utils/adt/inet_net_ntop.c

@@ -16,7 +16,7 @@
  */
 
 #if defined(LIBC_SCCS) && !defined(lint)
-static const char rcsid[] = "$Id: inet_net_ntop.c,v 1.14 2003/06/24 22:42:42 momjian Exp $";
+static const char rcsid[] = "$Id: inet_net_ntop.c,v 1.15 2003/06/25 01:08:13 momjian Exp $";
 #endif
 
 #include "postgres.h"
@@ -270,9 +270,9 @@ inet_cidr_ntop_ipv6(const u_char *src, int bits, char *dst, size_t size)
 
 	if (!double_colon) {
 		if (bits < 128 - 32)
-			cp += SPRINTF((cp, "::%d", bits));
+			cp += SPRINTF((cp, "::"));
 		else if (bits < 128 - 16)
-			cp += SPRINTF((cp, ":0%d", bits));
+			cp += SPRINTF((cp, ":0"));
 	}
 
 	/* Format CIDR /width. */