Re: Extension security improvement: Add support for extensions with an owned schema - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Extension security improvement: Add support for extensions with an owned schema
Date
Msg-id CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS=ctjg1j2Z-D3ng@mail.gmail.com
Whole thread Raw
In response to Re: Extension security improvement: Add support for extensions with an owned schema  (Sadeq Dousti <msdousti@gmail.com>)
Responses Re: Extension security improvement: Add support for extensions with an owned schema
List pgsql-hackers
On Sunday, July 27, 2025, Sadeq Dousti <msdousti@gmail.com> wrote:

(a) The patch affects DROP EXTENSION in that it drops the schema as well, if it's owned by the extension. This needs to be mentioned in the documentation. In addition, an extra confirmation (e.g., "This will drop schema nnnn as well, do you wish to continue?") when dropping the extension might be desired, as the extension schema could contain user data (e.g., pg_cron keeps the jobs and their execution details).

SQL isn’t interactive in this sense.  There isn’t a way to ask “are you sure?”.  At best the server can refuse to do something unless additional options, like “force/cascade” are present in the command.

David J.
 

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Non-text mode for pg_dumpall
Next
From: Sadeq Dousti
Date:
Subject: Re: Extension security improvement: Add support for extensions with an owned schema