Heikki Linnakangas <hlinnakan...@vmware.com> wrote: > Well, it's fairly harsh if the feature isn't working as > advertised.
Right -- there are people counting on serializable transaction to avoid data corruption (creation of data which violates the business rules which they believe are being enforced). A tuple freeze at the wrong moment could currently break that. The patch allows the guarantee to hold. The fact that this bug is only seen if there is a very-long-running transaction or if VACUUM FREEZE is run while data-modifying transactions are active does not eliminate the fact that without this patch data can be corrupted. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
