pgsql: Doc: improve description of which role runs a trigger.

Doc: improve description of which role runs a trigger. Refine wording from commit 01463e1cc. Author: Noah Misch Reviewed-by: Tom Lane Discussion: https://postgr.es/m/20250605163441.2f.nmi...@google.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c37be39a74b25

pgsql: nbtree: Remove useless row compare arg.

nbtree: Remove useless row compare arg. Use of a RowCompare key makes nbtree index scans ineligible to use pstate.forcenonrequired following recent bugfix commit 5f4d98d4. There's no longer any need for _bt_check_rowcompare to accept a forcenonrequired argument, so remove it. Branch -- master

pgsql: Avoid bogus scans of partitions when marking FKs enforced

Avoid bogus scans of partitions when marking FKs enforced Similar to commit cc733ed164c5: when an unenforced foreign key that references a partitioned table is altered to be enforced, we scan the constrained table based on each partition on the referenced partitioned table. This is bogus and like

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- REL_15_STABLE Details --

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- master Details --- https

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- REL_17_STABLE Details --

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- REL_16_STABLE Details --

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- REL_14_STABLE Details --

pgsql: Doc: you must own the target object to use SECURITY LABEL.

Doc: you must own the target object to use SECURITY LABEL. For some reason this wasn't mentioned before. Author: Patrick Stählin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46d...@packi.ch Backpatch-through: 13 Branch -- REL_13_STABLE Details --

pgsql: Avoid bogus scans of partitions when validating FKs to partition

Avoid bogus scans of partitions when validating FKs to partitioned tables Validating an unvalidated foreign key that references a partitioned table would try to queue validations for each individual partition of the referenced table, but this is wrong: each individual partition would not necessari

pgsql: Change role names used in trigger test.

Change role names used in trigger test. The choices made in commit 01463e1cc might pose copyright hazards, and are more cutesy than informative anyway. Reported-by: Noah Misch Author: Tom Lane Discussion: https://postgr.es/m/20250415155850.9b.nmi...@google.com Branch -- master Details ---

pgsql: psql: fix order of join clauses when listing extensions

psql: fix order of join clauses when listing extensions Commit d696406a9b2 added a new join to the query for extensions, but did so in the wrong place, causing the AND clause to be applied to the wrong join. Author: Suraj Kharage Reviewed-By: Dilip Kumar Discussion: https://postgr.es/m/CAF1DzP