Robert Haas 2e44770fa3 pgrowlocks: Use GetActiveSnapshot() rather than SnapshotNow. ... Per discussion, it's desirable to eliminate all remaining uses of SnapshotNow, because it has unpleasant semantics: race conditions can result in seeing multiple versions of a concurrently updated row, or none at all. By using GetActiveSnapshot() here, callers will see exactly those rows that would have been visible if the invoking query had scanned the table using, for example, a SELECT statement. This is slightly different from the old behavior, because commits that happen concurrently with the scan will not affect the results. In REPEATABLE READ or SERIALIZABLE modes, where transaction snapshots are used, commits that have happened since the start of the transaction will also not affect the results. It is hoped that this minor incompatibility will be thought an improvement, or at least no worse than what we did before.		2013-07-22 16:21:14 -04:00
..
Makefile	Improve concurrency of foreign key locking	2013-01-23 12:04:59 -03:00
pgrowlocks--1.0--1.1.sql	Fix typo in update scripts for some contrib modules.	2013-07-19 04:13:01 +09:00
pgrowlocks--1.1.sql	Improve concurrency of foreign key locking	2013-01-23 12:04:59 -03:00
pgrowlocks--unpackaged--1.0.sql
pgrowlocks.c	pgrowlocks: Use GetActiveSnapshot() rather than SnapshotNow.	2013-07-22 16:21:14 -04:00
pgrowlocks.control	Improve concurrency of foreign key locking	2013-01-23 12:04:59 -03:00