Re: proposal: schema variables

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, jian he <jian(dot)universality(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, DUVAL REMI <REMI(dot)DUVAL(at)cheops(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal: schema variables
Date: 2025-05-21 05:15:27
Message-ID: CAFj8pRAp1pWvJQ6uP_RDFMFRZfDqGz7beHGz0+eZJQ6o8nzv=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

út 20. 5. 2025 v 23:07 odesílatel Bruce Momjian <bruce(at)momjian(dot)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 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.
>
> 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(at)momjian(dot)us> https://momjian.us
> EDB https://enterprisedb.com
>
> Do not let urgent matters crowd out time for investment in the future.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniil Davydov 2025-05-21 05:31:59 Re: [BUG] Skipped initialization of some xl_xact_parsed_prepare fields
Previous Message Yasir 2025-05-21 05:01:56 Re: Violation of principle that plan trees are read-only

Browse pgsql-performance by date

  From Date Subject
Next Message Pavel Stehule 2025-05-21 05:49:34 Re: Re: proposal: schema variables
Previous Message Michael Paquier 2025-05-21 00:21:42 Re: Re: proposal: schema variables