While reading through the patch for what must be the 100th time by now, it occurred to me that this comment in heap_xlog_freeze:
+ /* + * Freezing tuples does not require conflict processing + */ is plain wrong. In the master, we can freeze the xmin of a tuple that's not yet visible to all read-only transactions in the standby. We do need conflict processing there. -- 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
