Alvaro Herrera c6cd27e36b Avoid resetting Xmax when it's a multi with an aborted update ... HeapTupleSatisfiesUpdate can very easily "forget" tuple locks while checking the contents of a multixact and finding it contains an aborted update, by setting the HEAP_XMAX_INVALID bit. This would lead to concurrent transactions not noticing any previous locks held by transactions that might still be running, and thus being able to acquire subsequent locks they wouldn't be normally able to acquire. This bug was introduced in commit 1ce150b7bb; backpatch this fix to 9.3, like that commit. This change reverts the change to the delete-abort-savept isolation test in 1ce150b7bb, because that behavior change was caused by this bug. Noticed by Andres Freund while investigating a different issue reported by Noah Misch.		2013-12-05 12:21:55 -03:00
..
examples	Update copyrights for 2013	2013-01-01 17:15:01 -05:00
isolation	Avoid resetting Xmax when it's a multi with an aborted update	2013-12-05 12:21:55 -03:00
locale	Run newly-configured perltidy script on Perl files.	2012-07-04 21:47:49 -04:00
mb	Lots of doc corrections.	2012-04-23 22:43:09 -04:00
performance	Run newly-configured perltidy script on Perl files.	2012-07-04 21:47:49 -04:00
regress	Fix crash in assign_collations_walker for EXISTS with empty SELECT list.	2013-12-02 20:28:49 -05:00
thread	Update copyrights for 2013	2013-01-01 17:15:01 -05:00
Makefile	Add isolation test to check-world and installcheck-world	2012-03-05 20:19:20 +02:00