Re: Batch replication ordering (was Re: [GENERAL] 32/64-bit - Mailing list pgsql-general

From Jan Wieck
Subject Re: Batch replication ordering (was Re: [GENERAL] 32/64-bit
Date
Msg-id 3E983059.3CD1517B@Yahoo.com
Whole thread Raw
In response to 32/64-bit transaction IDs?  ("Ed L." <pgsql@bluepolka.net>)
List pgsql-general
"Ed L." wrote:
> If the ordering I seek exists via the algorithm I've described, I don't

The right ordering is commit order, because that is the order that
played back serialized (without possible lock conflicts) guarantees the
same tuples hit.

Unfortunately I know of no sure way to tell the commit order. The
max(seqid) per transaction in ascending order would be a good
approximation at least.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-general by date:

Previous
From: Shridhar Daithankar
Date:
Subject: Re: How to drop column ?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Batch replication ordering (was Re: [GENERAL] 32/64-bit