Re: pg_get__*_ddl consolidation

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_get__*_ddl consolidation
Date: 2026-03-20 13:15:16
Message-ID: 202603201311.yhtqmvektawm@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Mar-19, Andrew Dunstan wrote:

> Greetings
>
> Euler Taveira and I have been working on consolidating these patches.

Hmm, did you remove the permissions checking to dump objects? I thought
we had concluded that these were needed -- ie. you have to have at least
CONNECT to a database to be able to dump it, and so on. This way, the
functions do not override a DBAs intention to hide the information, when
they run REVOKE on the catalogs. I know this is a nonstandard thing to
do, but some people do it nonetheless.

https://postgr.es/m/202511131446.uzn4c25ljmd4@alvherre.pgsql

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Computing is too important to be left to men." (Karen Spärck Jones)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-03-20 13:19:30 Re: Resetting snapshots during the first phase of [CREATE |RE]INDEX CONCURRENTLY
Previous Message Aleksander Alekseev 2026-03-20 13:02:10 Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions