MIME-Version: 1.0
In-Reply-To: 
 <CADE6LvjnX8MbZPSTkrdoRGwf+_q6deNN1+-N_bmjdUgvFNy+fQ@mail.gmail.com>
References: 
 <CAGECzQQzDqDzakBkR71ZkQ1N1ffTjAaruRSqppQAKu3WF+6rNQ@mail.gmail.com>
 <dbd3cc5a5edde04941c8624dde7e4bd2a063f366.camel@j-davis.com>
 <CAGECzQTe3y6xwP9aMbFBCxKnQEEn3G3=cEDqoD5xaOwPwypd_A@mail.gmail.com>
 <CAGECzQTAgtTp3G=Em3xEY=T=uiKfyu5xLYri9By=sfNBS5C_9A@mail.gmail.com>
 <CAKFQuwaT4_n=e0YKBZAyox1CQUra2ka0cySs+3pGZR5p50pn-g@mail.gmail.com>
 <CAGECzQTOJrnnJkmMe9nems0jouiKUbFcEb1rb9kE_svsAZiGQg@mail.gmail.com>
 <585e996c-a5c6-4e61-acc4-d92b7a1458ea@vondra.me>
 <CAGECzQS02M6YPDXemo36tShO-ZYObjqnyTJyVttua1PGyN4xRw@mail.gmail.com>
 <CADE6LvjnX8MbZPSTkrdoRGwf+_q6deNN1+-N_bmjdUgvFNy+fQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Sun, 27 Jul 2025 17:27:18 -0700
Message-ID: 
 <CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS=ctjg1j2Z-D3ng@mail.gmail.com>
Subject: Re: Extension security improvement: Add support for extensions with
 an owned schema
To: Sadeq Dousti <msdousti@gmail.com>
Cc: Jelte Fennema-Nio <me@jeltef.nl>, Tomas Vondra <tomas@vondra.me>,
 Jeff Davis <pgsql@j-davis.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
 "David E. Wheeler" <david@justatheory.com>,
	Artem Gavrilov <artem.gavrilov@percona.com>
Content-Type: multipart/alternative; boundary="000000000000c49bba063af25a2e"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS%3Dctjg1j2Z-D3ng%40mail.gmail.com>
Precedence: bulk

--000000000000c49bba063af25a2e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=99t interactive in this sense.  There isn=E2=80=99t a way to =
ask =E2=80=9Care you
sure?=E2=80=9D.  At best the server can refuse to do something unless addit=
ional
options, like =E2=80=9Cforce/cascade=E2=80=9D are present in the command.

David J.

--000000000000c49bba063af25a2e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sunday, July 27, 2025, Sadeq Dousti &lt;<a href=3D"mailto:msdousti@gmail=
.com">msdousti@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div dir=3D"ltr"><br>(a) The patch affects DROP EXTENSION in that it drops t=
he schema as well, if it&#39;s owned by the extension. This needs to be men=
tioned in the documentation. In addition, an extra confirmation<span class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"> (e.g., &quot;Th=
is will drop schema nnnn as well, do you wish to continue?&quot;)</span> wh=
en dropping the extension might be <span class=3D"gmail_default" style=3D"f=
ont-family:tahoma,sans-serif"></span>d<span class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">esired</span>, as the extension schema c=
ould contain user data (e.g., pg_cron keeps the jobs and their execution de=
tails).<br></div></blockquote><div><br></div><div>SQL isn=E2=80=99t interac=
tive in this sense.=C2=A0 There isn=E2=80=99t a way to ask =E2=80=9Care you=
 sure?=E2=80=9D.=C2=A0 At best the server can refuse to do something unless=
 additional options, like =E2=80=9Cforce/cascade=E2=80=9D are present in th=
e command.</div><div><br></div><div>David J.</div><div>=C2=A0</div>

--000000000000c49bba063af25a2e--