[HACKERS] A small mistake in the initial latestCompletedXid idea

2007-09-12 Thread Florian G. Pflug
Hi When I initially proposed to use the latest *committed* xid as the xmax instead of ReadNewTransactionId(), I believed that this would cause tuples created by a later aborted transaction not to be vacuumed until another transaction (with a higher xid) commits later. The idea was therefore

Re: [HACKERS] A small mistake in the initial latestCompletedXid idea

2007-09-12 Thread Tom Lane
Florian G. Pflug [EMAIL PROTECTED] writes: Therefore, I suggest that we rename latestCompletedXid to latestCommittedXid, and update it only on commits. Admittedly, this won't bring any measurable performance benefit in itself (it will slightly reduce the average snapshot size, though), but not

Re: [HACKERS] A small mistake in the initial latestCompletedXid idea

2007-09-12 Thread Florian G. Pflug
Tom Lane wrote: Florian G. Pflug [EMAIL PROTECTED] writes: Therefore, I suggest that we rename latestCompletedXid to latestCommittedXid, and update it only on commits. Admittedly, this won't bring any measurable performance benefit in itself (it will slightly reduce the average snapshot size,