Re: pg_dump needs SELECT privileges on irrelevant extension table

Jacob Champion <jchampion@timescale.com>

View thread

From: Jacob Champion <jchampion@timescale.com>

To: Andrew Dunstan <andrew@dunslane.net>, Akshat Jaimini <destrex271@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2023-08-09T23:10:39Z

Lists: pgsql-bugs, pgsql-hackers

Attachments

since-v2.diff.txt (text/plain)
v3-0001-Add-failing-test-for-undumped-extension-table.patch (text/x-patch) patch v3-0001
v3-0002-pg_dump-skip-lock-for-extension-tables-without-po.patch (text/x-patch) patch v3-0002
backport-11-0001.patch.txt (text/plain)
backport-11-0002.patch.txt (text/plain)

Hi all,

v3 fixes a doc comment I forgot to fill in; there are no other code
changes. To try to further reduce the activation energy, I've also
attached an attempt at a backport to 11. The main difference is the
absence of catalogIdHash, which showed up in 15, so we don't get the
benefit of that deduplication.

Thanks,
--Jacob

Commits

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

Don't try to dump RLS policies or security labels for extension objects.
- a70f2a57f233 17.0 landed
- 64d2467fc8d3 16.2 landed
- f15147df625f 15.6 landed
- 9e08789d4832 13.14 landed
- 891afa84c27e 12.18 landed
- 15439205d8ce 14.11 landed