Re: pg_dump needs SELECT privileges on irrelevant extension table
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <champion.p@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>, Andrew Dunstan <andrew@dunslane.net>,
Akshat Jaimini <destrex271@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Aleksander Alekseev <aleksander@timescale.com>
Date: 2023-11-09T19:02:51Z
Lists: pgsql-bugs, pgsql-hackers
I wrote: > Jacob Champion <champion.p@gmail.com> writes: >> Is this approach backportable? > The code fix would surely work in the back branches. Whether the > behavioral change is too big to be acceptable in minor releases > is something I don't have a strong opinion on. I'm hearing nothing but crickets :-( If nobody objects by say Monday, I'm going to go ahead and commit (and backpatch) the patch I posted at [1]. regards, tom lane [1] https://www.postgresql.org/message-id/2984517.1697577076%40sss.pgh.pa.us
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