Alvaro Herrera 47a3a13178 Fix deadlock hazard in CREATE INDEX CONCURRENTLY ... Multiple sessions doing CREATE INDEX CONCURRENTLY simultaneously are supposed to be able to work in parallel, as evidenced by fixes in commit c3d09b3bd2 specifically to support this case. In reality, one of the sessions would be aborted by a misterious "deadlock detected" error. Jeff Janes diagnosed that this is because of leftover snapshots used for system catalog scans -- this was broken by 8aa3e47510 keeping track of (registering) the catalog snapshot. To fix the deadlocks, it's enough to de-register that snapshot prior to waiting. Backpatch to 9.4, which introduced MVCC catalog scans. Include an isolationtester spec that 8 out of 10 times reproduces the deadlock with the unpatched code for me (Álvaro). Author: Jeff Janes Diagnosed-by: Jeff Janes Reported-by: Jeremy Finzel Discussion: https://postgr.es/m/CAMa1XUhHjCv8Qkx0WOr1Mpm_R4qxN26EibwCrj0Oor2YBUFUTg%40mail.gmail.com		2018-01-02 19:16:16 -03:00
..
examples	Include <sys/select.h> where needed	2016-09-27 01:05:21 -03:00
isolation	Fix deadlock hazard in CREATE INDEX CONCURRENTLY	2018-01-02 19:16:16 -03:00
locale	Rename 'gmake' to 'make' in docs and recommended commands	2014-02-12 17:29:19 -05: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
perl	Install TAP test infrastructure so it's available for extension testing.	2016-09-23 15:50:00 -04:00
regress	Fix non-GNU makefiles for AIX make.	2017-11-30 00:57:32 -08:00
thread	Update copyright for 2014	2014-01-07 16:05:30 -05:00
Makefile	Install TAP test infrastructure so it's available for extension testing.	2016-09-23 15:50:00 -04:00