Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Manfred Koizar wrote:
On Wed, 11 Jun
On Wed, 11 Jun 2003 09:05:33 -0400, Tom Lane [EMAIL PROTECTED]
wrote:
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
If a transaction marks a tuple for update and later commits without
actually having updated the tuple, do we still need the information
that the tuple has once been reserved for an update or can we simply
set the HEAP_XMAX_INVALID hint bit of the tuple?
In other words, is this snippet from a
Manfred Koizar [EMAIL PROTECTED] writes:
If a transaction marks a tuple for update and later commits without
actually having updated the tuple, do we still need the information
that the tuple has once been reserved for an update or can we simply
set the HEAP_XMAX_INVALID hint bit of the tuple?
