Amit Kapila 3ba59ccc89 Allow page lock to conflict among parallel group members. ... This is required as it is no safer for two related processes to perform clean up in gin indexes at a time than for unrelated processes to do the same. After acquiring page locks, we can acquire relation extension lock but reverse never happens which means these will also not participate in deadlock. So, avoid checking wait edges from this lock. Currently, the parallel mode is strictly read-only, but after this patch we have the infrastructure to allow parallel inserts and parallel copy. Author: Dilip Kumar, Amit Kapila Reviewed-by: Amit Kapila, Kuntal Ghosh and Sawada Masahiko Discussion: https://postgr.es/m/CAD21AoCmT3cFQUN4aVvzy5chw7DuzXrJCbrjTU05B+Ss=Gn1LA@mail.gmail.com		2020-03-21 08:48:06 +05:30
..
buffer	Introduce a maintenance_io_concurrency setting.	2020-03-16 17:14:26 +13:00
file	Remove HAVE_WORKING_LINK	2020-03-11 11:23:04 +01:00
freespace	Update copyrights for 2020	2020-01-01 12:21:45 -05:00
ipc	Don't use EV_CLEAR for kqueue events.	2020-03-18 13:05:09 +13:00
large_object	Remove utils/acl.h from catalog/objectaddress.h	2020-03-10 10:27:00 +01:00
lmgr	Allow page lock to conflict among parallel group members.	2020-03-21 08:48:06 +05:30
page	Add missing errcode() in a few ereport calls.	2020-03-18 09:27:14 +05:30
smgr	Refactor confusing code in _mdfd_openseg().	2020-01-27 09:12:56 +13:00
sync	Fix typos.	2020-02-10 09:31:18 +05:30
Makefile	Refactor the fsync queue for wider use.	2019-04-04 23:38:38 +13:00