From: Florents Tselai <florents.tselai@gmail.com>
Message-Id: <8ACA6321-D78B-4FBB-9685-8F51BF635115@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_AF2997B5-44ED-4553-A813-977C20329C4A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Subject: Re: SQL function to access to `creating_extension`
Date: Sat, 19 Apr 2025 12:52:40 +0300
In-Reply-To: <CAG=VW17kAweKGwqtVU8vn71uRCOS9yxnyEnoa=-3sAuyZt5O6g@mail.gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
To: Yurii Rashkovskii <yrashk@omnigres.com>
References: <CAG=VW17kAweKGwqtVU8vn71uRCOS9yxnyEnoa=-3sAuyZt5O6g@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/8ACA6321-D78B-4FBB-9685-8F51BF635115%40gmail.com>
Precedence: bulk


--Apple-Mail=_AF2997B5-44ED-4553-A813-977C20329C4A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 19 Apr 2025, at 4:18=E2=80=AFAM, Yurii Rashkovskii =
<yrashk@omnigres.com> wrote:
>=20
> Hi,
>=20
> I propose to introduce `pg_creating_extension()` function that would =
return the OID of the extension being currently created (or `null` if =
none is).
>=20
> The core motivation for it is to be able to establish data provenance =
in tables created by extensions to be used in `pg_extension_config_dump` =
configuration. This way, even if a secondary extension inserts data, it =
can still be excluded from the dump by tracking data provenance in a =
column with a default. Something like
>=20
> ```
> create table my_config (
>    --- ...
>    extension_provenance oid default pg_creating_extension()
> )
> ```
>=20
> This would allow for a generalized exclusion in =
pg_extension_config_dump.
>=20
> I've attached a draft patch for this simple function. I am happy to =
finalize it with tests and documentation if there is a consensus on the =
shape.
>=20
> --
> Founder at Omnigres
> https://omnigres.com =
<https://omnigres.com/><v1-0001-pg_creating_extension-to-inspect-if-an-ext=
ension-is-.patch>


Hi Yurii, =20

+1 from me. =20

I can see this being helpful, especially when dealing with shared tables =
or managing extension-specific data in configuration dumps.


--Apple-Mail=_AF2997B5-44ED-4553-A813-977C20329C4A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On 19 Apr 2025, at 4:18=E2=80=AFAM, Yurii Rashkovskii =
&lt;yrashk@omnigres.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div dir=3D"ltr">Hi,<br><br>I =
propose to introduce `pg_creating_extension()` function that would =
return the OID of the extension being currently created (or `null` if =
none is).<br><br>The core motivation for it is to be able to establish =
data provenance in tables created by extensions to be used in =
`pg_extension_config_dump` configuration. This way, even if a secondary =
extension inserts data, it can still be excluded from the dump by =
tracking data provenance in a column with a default. Something =
like<div><br></div><div>```</div><div>create table my_config =
(</div><div>&nbsp; &nbsp;--- ...</div><div>&nbsp; =
&nbsp;extension_provenance oid default =
pg_creating_extension()</div><div>)</div><div>```<br><br>This would =
allow for a generalized exclusion in =
pg_extension_config_dump.<br><br>I've attached a draft patch for this =
simple function. I am happy to finalize it with tests and documentation =
if there is a consensus on the shape.</div><div><br>--<br>Founder at =
Omnigres<br><a =
href=3D"https://omnigres.com/">https://omnigres.com</a></div></div>
<span =
id=3D"cid:f_m9nj4bmo0">&lt;v1-0001-pg_creating_extension-to-inspect-if-an-=
extension-is-.patch&gt;</span></div></blockquote></div><br><div><br></div>=
<div>Hi Yurii, &nbsp;</div><div><br></div><div>+1 from me. =
&nbsp;</div><div><br></div><div>I can see this being helpful, especially =
when dealing with shared tables or managing extension-specific data in =
configuration dumps.</div><div><br></div></body></html>=

--Apple-Mail=_AF2997B5-44ED-4553-A813-977C20329C4A--