Re: Assorted improvements in pg_dump

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Andres Freund <andres@anarazel.de>

Cc: Hans Buschmann <buschmann@nidsa.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-12-03T21:33:42Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_dump: avoid unsafe function calls in getPolicies().
- b7333e826955 11.19 landed
- a5b26aaafe4f 13.10 landed
- 1ed6f1b9116c 12.14 landed
- 03ac48549438 14.7 landed
- 3e6e86abca01 15.0 landed
Postpone calls of unsafe server-side functions in pg_dump.
- e46e986baef0 13.10 landed
- b1f106420b1a 11.19 landed
- 55f30e6c7640 14.7 landed
- 344b7849200f 12.14 landed
- e3fcbbd623b9 15.0 landed
Account for TOAST data while scheduling parallel dumps.
- 65aaed22a849 15.0 landed
Use PREPARE/EXECUTE for repetitive per-object queries in pg_dump.
- be85727a3df7 15.0 landed
Avoid per-object queries in performance-critical paths in pg_dump.
- 9895961529ef 15.0 landed
Rethink pg_dump's handling of object ACLs.
- 0c9d84427f44 15.0 landed
Refactor pg_dump's tracking of object components to be dumped.
- 5209c0ba0bfd 15.0 landed
pg_dump: fix mis-dumping of non-global default privileges.
- 2acc84c6fd29 15.0 cited

Attachments

0001-fix-component-masking-3.patch (text/x-diff) patch 0001
0002-rethink-ACL-handling-3.patch (text/x-diff) patch 0002
0003-move-unsafe-function-calls-3.patch (text/x-diff) patch 0003
0004-bulk-queries-3.patch (text/x-diff) patch 0004
0005-fix-toast-sched-3.patch (text/x-diff) patch 0005
0006-prepare-repeated-queries-4.patch (text/x-diff) patch 0006

Here's an updated version of this patch set.  The only non-line-number
changes are

(1) in 0004, I dealt with the issue of not having unnest() in old branches
by bumping the minimum remote server version to 8.4.  Seeing that we seem
to have consensus in the other thread to push the minimum up to somewhere
around 9.2, I see no point in making this patch put in conditional code
that we'd shortly rip out again.

(2) I also added some comments to 0004 to hopefully address Justin's
confusion about string lengths.

I feel quite fortunate that a month's worth of commitfest hacking
didn't break any of these patches.  Unless someone intends to
review these more thoroughly than they already have, I'd like to
go ahead and push them.

			regards, tom lane