MIME-Version: 1.0
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>
 <CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS=ctjg1j2Z-D3ng@mail.gmail.com>
In-Reply-To: 
 <CAKFQuwYceVNWLUcX-OHw68G3d7WUDdDioTvS=ctjg1j2Z-D3ng@mail.gmail.com>
From: Sadeq Dousti <msdousti@gmail.com>
Date: Mon, 28 Jul 2025 02:45:21 +0200
Message-ID: 
 <CADE6Lvh9hBvLJm_X73w+=bo3B9EH9gzM=cGx1AFOsmCEP4Vm5Q@mail.gmail.com>
Subject: Re: Extension security improvement: Add support for extensions with
 an owned schema
To: "David G. Johnston" <david.g.johnston@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="000000000000f113a1063af29b3a"
Archived-At: 
 <https://www.postgresql.org/message-id/CADE6Lvh9hBvLJm_X73w%2B%3Dbo3B9EH9gzM%3DcGx1AFOsmCEP4Vm5Q%40mail.gmail.com>
Precedence: bulk

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

You're absolutely right about the lack of interactivity. I'd still go with
your suggestion of using something along the lines of cascade/force, as
dropping the schema silently can potentially delete the user data.

Bests,
Sadeq

On Mon, Jul 28, 2025, 02:27 David G. Johnston <david.g.johnston@gmail.com>
wrote:

> 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 t=
o ask =E2=80=9Care you
> sure?=E2=80=9D.  At best the server can refuse to do something unless add=
itional
> options, like =E2=80=9Cforce/cascade=E2=80=9D are present in the command.
>
> David J.
>
>

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

<div dir=3D"auto">You&#39;re absolutely right about the lack of interactivi=
ty. I&#39;d still go with your suggestion of using something along the=C2=
=A0lines of cascade/force, as dropping the schema silently can potentially =
delete the user data.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">Be=
sts,=C2=A0</div><div dir=3D"auto">Sadeq=C2=A0</div></div><br><div class=3D"=
gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Mon, Jul 28, 2025, 02:27 David G. Johnston &lt;<a href=3D"mailto:david.g.j=
ohnston@gmail.com">david.g.johnston@gmail.com</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">On Sunday, July 27, 2025, Sade=
q Dousti &lt;<a href=3D"mailto:msdousti@gmail.com" target=3D"_blank" rel=3D=
"noreferrer">msdousti@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div dir=3D"ltr"><br>(a) The patch affects DROP EX=
TENSION in that it drops the schema as well, if it&#39;s owned by the exten=
sion. This needs to be mentioned in the documentation. In addition, an extr=
a confirmation<span class=3D"gmail_default" style=3D"font-family:tahoma,san=
s-serif"> (e.g., &quot;This will drop schema nnnn as well, do you wish to c=
ontinue?&quot;)</span> when dropping the extension might be <span class=3D"=
gmail_default" style=3D"font-family:tahoma,sans-serif"></span>d<span class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">esired</span>, a=
s the extension schema could contain user data (e.g., pg_cron keeps the job=
s and their execution details).<br></div></blockquote><div><br></div><div>S=
QL isn=E2=80=99t interactive 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 refus=
e to do something unless additional options, like =E2=80=9Cforce/cascade=E2=
=80=9D are present in the command.</div><div><br></div><div>David J.</div><=
div>=C2=A0</div>
</blockquote></div>

--000000000000f113a1063af29b3a--