public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Bruce Momjian <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: Marcos Pegoraro <[email protected]>
Cc: Pavel Stehule <[email protected]>
Cc: jian he <[email protected]>
Cc: Dmitry Dolgov <[email protected]>
Cc: Erik Rijkers <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Amit Kapila <[email protected]>
Cc: DUVAL REMI <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: proposal: schema variables
Date: Tue, 20 May 2025 22:36:54 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <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>
<[email protected]>
<CAB-JLwY2-Hm_SYbj2td_VKuU8awCwgDr-sOtjHRE2C-Sgg_pFg@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
On Tue, 2025-05-20 at 16:28 -0400, Bruce Momjian wrote:
> On Tue, May 20, 2025 at 08:47:36PM +0200, Daniel Gustafsson wrote:
> > > On 20 May 2025, at 18:39, Bruce Momjian <[email protected]> wrote:
> > > 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.
> > >
> > > 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 =)
>
> 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 posting
> 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 that
> direction.
>
> Now, of course, if I am the only one who feels this way, I can suppress
> these emails on my end.
In my opinion, this patch set is adding something that would be valuable 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.
Yours,
Laurenz Albe
view thread (439+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: proposal: schema variables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox