Nov 2022

2 commits
pg_dump: avoid unsafe function calls in getPolicies().
19 Nov 2022Tom LaneREL_14_STABLE14.7REL_13_STABLE13.10REL_12_STABLE12.14REL_11_STABLE11.19Also in: pg_dump does way too much before acquiring table locks (not this thread)Also in: Assorted improvements in pg_dump (not this thread)
LLM analysis, 100% surewritten from the discussion, no matching patch

This PostgreSQL 14 change filters getPolicies() server-side using selected table OIDs rather than discarding unwanted policies afterward. It has no matching attachment in #4 and corresponds to Tom Lane's additional backport described in #5.

Postpone calls of unsafe server-side functions in pg_dump.
19 Nov 2022Tom LaneREL_14_STABLE14.7REL_13_STABLE13.10REL_12_STABLE12.14REL_11_STABLE11.19Also in: pg_dump does way too much before acquiring table locks (landed as posted)Also in: Assorted improvements in pg_dump (not this thread)
LLM analysis, 100% suremodified before commitlight changesfrom patchset #4

Applying the PostgreSQL 14 attachment from #4 to the commit's parent reproduces the change except for freeing partkeydef, correcting a partition comment, and whitespace cleanup in pg_dump.c and pg_dump.h. The commit explicitly credits Tom Lane with the original patch and Gilles Darold with adapting the backport.

Credits across 2 commits

Author
Tom LaneLLM2
Committer
Tom Lane2

N LLM means N of the credits come from LLM analysis, not from commit trailers.