| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sadeq Dousti <msdousti(at)gmail(dot)com> |
| Cc: | Jelte Fennema-Nio <me(at)jeltef(dot)nl>, Tomas Vondra <tomas(at)vondra(dot)me>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Artem Gavrilov <artem(dot)gavrilov(at)percona(dot)com> |
| Subject: | Re: Extension security improvement: Add support for extensions with an owned schema |
| Date: | 2025-07-28 00:27:18 |
| Message-ID: | CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS=ctjg1j2Z-D3ng@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sunday, July 27, 2025, Sadeq Dousti <msdousti(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sadeq Dousti | 2025-07-28 00:45:21 | Re: Extension security improvement: Add support for extensions with an owned schema |
| Previous Message | Noah Misch | 2025-07-27 23:56:28 | Re: Non-text mode for pg_dumpall |