MIME-Version: 1.0
References: 
 <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> <41D2EE98-224D-4B43-9F8B-127525A99CD7@yesql.se>
 <aCzl0SQYGTBJfdtY@momjian.us>
 <138d50cd8d9617469922eb0017956a3610089064.camel@cybertec.at>
 <aCzu84eWXnXPvFmf@momjian.us>
In-Reply-To: <aCzu84eWXnXPvFmf@momjian.us>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Wed, 21 May 2025 07:15:27 +0200
Message-ID: 
 <CAFj8pRAp1pWvJQ6uP_RDFMFRZfDqGz7beHGz0+eZJQ6o8nzv=Q@mail.gmail.com>
Subject: Re: proposal: schema variables
To: Bruce Momjian <bruce@momjian.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
 Daniel Gustafsson <daniel@yesql.se>,
	Marcos Pegoraro <marcos@f10.com.br>, jian he <jian.universality@gmail.com>,
	Dmitry Dolgov <9erthalion6@gmail.com>, 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-Type: multipart/alternative; boundary="000000000000658a7906359e766b"
Archived-At: 
 <https://www.postgresql.org/message-id/CAFj8pRAp1pWvJQ6uP_RDFMFRZfDqGz7beHGz0%2BeZJQ6o8nzv%3DQ%40mail.gmail.com>
Precedence: bulk

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

=C3=BAt 20. 5. 2025 v 23:07 odes=C3=ADlatel Bruce Momjian <bruce@momjian.us=
> napsal:

> On Tue, May 20, 2025 at 10:36:54PM +0200, Laurenz Albe wrote:
> > On Tue, 2025-05-20 at 16:28 -0400, Bruce Momjian wrote:
> > > Well, we do have a right, e.g., we would not allow someone to
> repeatedly
> > > post patches for a Postgres extension we don't manage, or the jdbc
> > > driver.  I also don't think we would allow someone to continue postin=
g
> > > patches for a feature we have decided to reject, and I think we have
> > > decided to reject the patch in in its current form.  I think we might
> > > accept a trimmed-down version, but I don't see the patch moving in th=
at
> > > direction.
> > >
> > > Now, of course, if I am the only one who feels this way, I can suppre=
ss
> > > these emails on my end.
> >
> > In my opinion, this patch set is adding something that would be valuabl=
e
> to
> > have in core.
> >
> > If no committer intends to pick it up and commit it, I think the proper
> > action would be to step up and reject the patch set, not complain about
> the
> > insistence of the author.
>
> Are you saying I should not complain until we have officially rejected
> the patch set?  If we officially reject it, the patch author would no
> longer post it?
>

I'll respect committers. I really don't want to worry people in the
community. It is not my way, and I am sorry.

I think this is an important feature - for some group of developers, and
then I push my energy and time for this.
On the other hand, I accept that there is a lot of work that is important
for a wider group of users. So it is. Unfortunately,
without parser's hooks this feature cannot be implemented as an extension.
But parser's hooks was proposed,
and rejected, so there is no other possibility, how to do it. More -
implementation of this feature as an extension is not
best way.

regards

Pavel


>
> --
>   Bruce Momjian  <bruce@momjian.us>        https://momjian.us
>   EDB                                      https://enterprisedb.com
>
>   Do not let urgent matters crowd out time for investment in the future.
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">=C3=BAt 20. 5. =
2025 v=C2=A023:07 odes=C3=ADlatel Bruce Momjian &lt;<a href=3D"mailto:bruce=
@momjian.us">bruce@momjian.us</a>&gt; napsal:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">On Tue, May 20, 2025 at 10:36:54PM +0200, Lau=
renz Albe wrote:<br>
&gt; On Tue, 2025-05-20 at 16:28 -0400, Bruce Momjian wrote:<br>
&gt; &gt; Well, we do have a right, e.g., we would not allow someone to rep=
eatedly<br>
&gt; &gt; post patches for a Postgres extension we don&#39;t manage, or the=
 jdbc<br>
&gt; &gt; driver.=C2=A0 I also don&#39;t think we would allow someone to co=
ntinue posting<br>
&gt; &gt; patches for a feature we have decided to reject, and I think we h=
ave<br>
&gt; &gt; decided to reject the patch in in its current form.=C2=A0 I think=
 we might<br>
&gt; &gt; accept a trimmed-down version, but I don&#39;t see the patch movi=
ng in that<br>
&gt; &gt; direction.<br>
&gt; &gt; <br>
&gt; &gt; Now, of course, if I am the only one who feels this way, I can su=
ppress<br>
&gt; &gt; these emails on my end.<br>
&gt; <br>
&gt; In my opinion, this patch set is adding something that would be valuab=
le to<br>
&gt; have in core.<br>
&gt; <br>
&gt; If no committer intends to pick it up and commit it, I think the prope=
r<br>
&gt; action would be to step up and reject the patch set, not complain abou=
t the<br>
&gt; insistence of the author.<br>
<br>
Are you saying I should not complain until we have officially rejected<br>
the patch set?=C2=A0 If we officially reject it, the patch author would no<=
br>
longer post it?<br></blockquote><div><br></div><div>I&#39;ll respect commit=
ters. I really don&#39;t want to worry people in the community. It is not m=
y way, and I am sorry.</div><div><br></div><div>I think this is an importan=
t feature - for some group of developers, and then I push my energy and tim=
e for this. <br></div><div>On the other hand, I accept that there is a lot =
of work that is important for a wider group of users. So it is. Unfortunate=
ly,</div><div>without parser&#39;s hooks this feature cannot be implemented=
 as an extension. But parser&#39;s hooks was proposed,</div><div>and reject=
ed, so there is no other possibility, how to do it. More - implementation o=
f this feature as an extension is not</div><div>best way. <br></div><div><b=
r></div><div>regards</div><div><br></div><div>Pavel</div><div><br></div><di=
v><br></div><div><br></div><div><br></div><div><br></div><div><br></div><di=
v>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
=C2=A0 Bruce Momjian=C2=A0 &lt;<a href=3D"mailto:bruce@momjian.us" target=
=3D"_blank">bruce@momjian.us</a>&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"=
https://momjian.us" rel=3D"noreferrer" target=3D"_blank">https://momjian.us=
</a><br>
=C2=A0 EDB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a hr=
ef=3D"https://enterprisedb.com" rel=3D"noreferrer" target=3D"_blank">https:=
//enterprisedb.com</a><br>
<br>
=C2=A0 Do not let urgent matters crowd out time for investment in the futur=
e.<br>
</blockquote></div></div>

--000000000000658a7906359e766b--