On 21.01.2011 11:10, Simon Riggs wrote:
So any xid that commits in a different sequence to the order in which the xid was assigned creates a potential for unserialization? Or?
It's not the order in which the xid was assigned that matters, but the order the transactions started and got their snapshots. The xids might be assigned a lot later, after the transactions have already read data.
On HS we know the order of arrival of xids, and we know the order of commits, so we should be able to work out which are the potentially unserializable snapshots. That would allow us to make the standby independent of the master, thereby avoiding all this messy information flow.
Unfortunately although we know the order of arrival of xids, it doesn't tell us the order the transactions started.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
