Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\))
Subject: Re: proposal: schema variables
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <aCywNzDx2J3jrY1-@momjian.us>
Date: Tue, 20 May 2025 20:47:36 +0200
Cc: Marcos Pegoraro <marcos@f10.com.br>,
 Pavel Stehule <pavel.stehule@gmail.com>,
 jian he <jian.universality@gmail.com>,
 Dmitry Dolgov <9erthalion6@gmail.com>,
 Laurenz Albe <laurenz.albe@cybertec.at>,
 Erik Rijkers <er@xs4all.nl>,
 Michael Paquier <michael@paquier.xyz>,
 Amit Kapila <amit.kapila16@gmail.com>,
 DUVAL REMI <REMI.DUVAL@cheops.fr>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <41D2EE98-224D-4B43-9F8B-127525A99CD7@yesql.se>
References: 
 <CAFj8pRC9WKvJm22wfPExiSfQkn4r7mbHntPk11Ohh-50Avw9Bg@mail.gmail.com>
 <CAFj8pRDw=WVEdAnrLsFGstDaGtY4wNQdz59rpZEpZsVF3p0nfA@mail.gmail.com>
 <CAFj8pRC_2tHski1K4hUMZm0+T4y7na4d8hwgMMF7Y0MXhfUhbg@mail.gmail.com>
 <CAB-JLwaOdMQN838Fy2r2qZLTExfJp0zcjQjmOFVRXhW_-uDNVw@mail.gmail.com>
 <CAFj8pRArtw+Qqzk+Zf2NxjgO=paCBdc54eEma+MsVwtx3j7Atg@mail.gmail.com>
 <CAFj8pRAK_8ym1J=SAdin-vtL0PAachXgjWgU3QrhzinRdBX2sw@mail.gmail.com>
 <CAFj8pRAx-Gb9Ux825cxGNm38qQUOrij1GY6erPRaQ=cpqfiX7g@mail.gmail.com>
 <CAFj8pRCEjG005L=1vGbir-odYdcYxByOAeFVJ_K9eRcRF=MbNQ@mail.gmail.com>
 <aCyYHXhAjXOUPvLO@momjian.us>
 <CAB-JLwY2-Hm_SYbj2td_VKuU8awCwgDr-sOtjHRE2C-Sgg_pFg@mail.gmail.com>
 <aCywNzDx2J3jrY1-@momjian.us>
To: Bruce Momjian <bruce@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/41D2EE98-224D-4B43-9F8B-127525A99CD7%40yesql.se>
Precedence: bulk

> On 20 May 2025, at 18:39, Bruce Momjian <bruce@momjian.us> wrote:
>=20
> On Tue, May 20, 2025 at 01:33:18PM -0300, Marcos Pegoraro wrote:
>> Em ter., 20 de mai. de 2025 =C3=A0s 11:56, Bruce Momjian =
<bruce@momjian.us>
>> escreveu:
>>=20
>>    I will again ask why this patch set is being reposted when there =
is no
>>    plan to apply it to git master
>>=20
>> Too bad. I would love to have this functionality, from the user's =
point of view
>> there are problems where it would solve them wonderfully. I don't =
know
>> technically of what prevents it from being natively on core, but it =
would be
>> great, it would definitely be.
>=20
> My only point is that we should only be using email lists for work =
that
> is being actively worked on to be added to community Postgres.  There
> has been talk of a trimmed-down version of this being applied, but I
> don't see any work in that direction.
>=20
> This patch should be moved to a separate location where perhaps people
> can subscribe to updates when they are posted, perhaps github.

As a project with no roadmap governed by open forum consensus I don't =
think we
have any right to tell community members what they can or cannot work on =
here,
any technical discussion which conforms with our published policies =
should be
welcome.  If Pavel want's to continue rebasing his patchset here then he =
has,
IMHO, every right to do so.

Whether or not a committer will show interest at some point is another =
thing,
but we are seeing a very good role-model for taking responsibility for =
ones
work here at the very least =3D)

--
Daniel Gustafsson