Message-ID: <3318006a000e05360c487189bf8abe5c40732ce3.camel@cybertec.at>
Subject: Re: Extension disappearing act
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Dominique Devienne <ddevienne@gmail.com>, 
	pgsql-general@lists.postgresql.org
Date: Thu, 19 Jun 2025 18:35:55 +0200
In-Reply-To: <CAFCRh-_TQagsob_YH0nXktwhuBftNaiZ_VZ4REhZdSEkWXVKXg@mail.gmail.com>
References: 
	<CAFCRh-_TQagsob_YH0nXktwhuBftNaiZ_VZ4REhZdSEkWXVKXg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/3318006a000e05360c487189bf8abe5c40732ce3.camel%40cybertec.at>
Precedence: bulk

On Thu, 2025-06-19 at 15:09 +0200, Dominique Devienne wrote:
> Hi. Little mystery we don't understand. v17.
>=20
> Create new DB, owned by dedicated new ROLE.
> Create extension (pgcrypto) in our case. Installed in public, owned by
> DB owner role.
> Create schemas and populate them inside the DB.
> This also creates roles associated to those schemas.
> One of the schema is owned by the DB owner (in case that matters).
> Creates functions using pgcrypto, in some of those schemas.
> Drop all schemas (and associated roles), thus pgcrypto-using functins are=
 gone.
> Of course, the DB owner role was not dropped. Can't in fact.
> Somehow, the pgcrypto extension has disappeared, as side-effects of the d=
rops.
> We did a LIBPQ trace of the command to does all the drops,
> and there's no explicit drop of the extension.
>=20
> All of the above is done using a LOGIN role that has CREATEROLE and CREAT=
EDB.
>=20
> Extensions are not supposed to implicitly disappear, are they?
> Any idea, what we're missing, that might explain pgcrypto's disappearance=
?
> We're stumped for now.

So are we.  Why do you keep us guessing instead of posting a reproducer?

Yours,
Laurenz Albe