pgsql: Revert changes in execMain.c from commit 16828d5c0273b

Revert changes in execMain.c from commit 16828d5c0273b These changes were put in at some stage of the development process, but are unnecessary and should not have made it into the final patch. Mea culpa. Per gripe from Andreas Freund Backpatch to REL_11_STABLE Branch -- REL_11_STABLE

pgsql: Revert changes in execMain.c from commit 16828d5c0273b

Revert changes in execMain.c from commit 16828d5c0273b These changes were put in at some stage of the development process, but are unnecessary and should not have made it into the final patch. Mea culpa. Per gripe from Andreas Freund Backpatch to REL_11_STABLE Branch -- master Details

pgsql: Handle parallel index builds on mapped relations.

Handle parallel index builds on mapped relations. Commit 9da0cc35284, which introduced parallel CREATE INDEX, failed to propagate relmapper.c backend local cache state to parallel worker processes. This could result in parallel index builds against mapped catalog relations where the leader

pgsql: Handle parallel index builds on mapped relations.

Handle parallel index builds on mapped relations. Commit 9da0cc35284, which introduced parallel CREATE INDEX, failed to propagate relmapper.c backend local cache state to parallel worker processes. This could result in parallel index builds against mapped catalog relations where the leader

pgsql: Cosmetic cleanups in initdb.c.

Cosmetic cleanups in initdb.c. Commit bcbd94080 didn't bother to fix up a comment it had falsified. Also, const-ify choose_dsm_implementation(), since what it's returning is always a constant string; pickier compilers would warn about this. Branch -- master Details ---

pgsql: Improve TRUNCATE by avoiding early lock queue

Improve TRUNCATE by avoiding early lock queue A caller of TRUNCATE could previously queue for an access exclusive lock on a relation it may not have permission to truncate, potentially interfering with users authorized to work on it. This can be very intrusive depending on the lock attempted to

pgsql: Fix typo in SP-GiST error message

Fix typo in SP-GiST error message Error message didn't match the actual check. Fix that. Compression of leaf SP-GiST values was introduced in 11. So, backpatch. Discussion: https://postgr.es/m/20180810.100742.15469435.horiguchi.kyotaro%40lab.ntt.co.jp Author: Kyotaro Horiguchi

pgsql: Fix typo in SP-GiST error message

Fix typo in SP-GiST error message Error message didn't match the actual check. Fix that. Compression of leaf SP-GiST values was introduced in 11. So, backpatch. Discussion: https://postgr.es/m/20180810.100742.15469435.horiguchi.kyotaro%40lab.ntt.co.jp Author: Kyotaro Horiguchi

pgsql: Add missing documentation for argument of amcostestimate()

Add missing documentation for argument of amcostestimate() 5262f7a4fc44 have introduced parallel index scan. In order to estimate the number of parallel workers, it adds extra argument to amcostestimate() index access method API function. However, this extra argument was missed in the

pgsql: Add missing documentation for argument of amcostestimate()

Add missing documentation for argument of amcostestimate() 5262f7a4fc44 have introduced parallel index scan. In order to estimate the number of parallel workers, it adds extra argument to amcostestimate() index access method API function. However, this extra argument was missed in the

pgsql: Add missing documentation for argument of amcostestimate()

Add missing documentation for argument of amcostestimate() 5262f7a4fc44 have introduced parallel index scan. In order to estimate the number of parallel workers, it adds extra argument to amcostestimate() index access method API function. However, this extra argument was missed in the

pgsql: Fix misspelled pg_trgm contrib name in PostgreSQL 11 release not

Fix misspelled pg_trgm contrib name in PostgreSQL 11 release notes Author: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoD0Eii9y9f3cQV9AsaUF%3DMmOrQuZLHqoobFp%3DmSKEx1CA%40mail.gmail.com Branch -- master Details ---