aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/drop_user.sgml
diff options
context:
space:
mode:
authorAmit Langote <amitlan@postgresql.org>2025-05-22 14:17:24 +0900
committerAmit Langote <amitlan@postgresql.org>2025-05-22 17:02:35 +0900
commit1722d5eb05d8e5d2e064cd1798abcae4f296ca9d (patch)
tree6661dfcd476b8e355f4f05d38badbe1c6de2ed36 /doc/src/sgml/ref/drop_user.sgml
parentf3622b64762bb5ee5242937f0fadcacb1a10f30e (diff)
downloadpostgresql-master.tar.gz
postgresql-master.zip
Revert "Don't lock partitions pruned by initial pruning"HEADmaster
As pointed out by Tom Lane, the patch introduced fragile and invasive design around plan invalidation handling when locking of prunable partitions was deferred from plancache.c to the executor. In particular, it violated assumptions about CachedPlan immutability and altered executor APIs in ways that are difficult to justify given the added complexity and overhead. This also removes the firstResultRels field added to PlannedStmt in commit 28317de72, which was intended to support deferred locking of certain ModifyTable result relations. Reported-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/605328.1747710381@sss.pgh.pa.us
Diffstat (limited to 'doc/src/sgml/ref/drop_user.sgml')
0 files changed, 0 insertions, 0 deletions