Re: proposal: schema variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: schema variables
Date
Msg-id CAFj8pRBNQCycGvGjxKumEgKL+Dqxm8QXY-v0xhBVm+0T3Snbgg@mail.gmail.com
Whole thread Raw
In response to Re: proposal: schema variables  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers


st 21. 5. 2025 v 8:27 odesílatel Laurenz Albe <laurenz.albe@cybertec.at> napsal:
On Tue, 2025-05-20 at 17:06 -0400, Bruce Momjian wrote:
> f 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?

No, you are free to complain, just as Pavel is free to keep his patch
set from rotting.  What I am trying to say is that rejecting the patch
set is the most effective way to complain.

The current state is that Pavel keeps the patch set alive, and occasionally
people review it or parts of it.  But no committer is accepting or rejecting
it, so the patch set remains in limbo.  This annoys you, and it is certainly
not a happy experience for the author.  Rejection is not nice, but at least
it would make it easier for Pavel to move on and spend his energy elsewhere.

Rejection is not nice, but it can be, and if it will be, I hope, there will be more cleaner
status if we want this feature or not, and if possibly want this feature, what we expect.

This feature can be designed differently in respect to some priorities. But without known
priorities, any patch, proposal can end in the same state.

Regards

Pavel

 

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: 노명석
Date:
Subject: psql : \dn+ to show default schema privileges
Next
From: Bertrand Drouvot
Date:
Subject: Re: Avoid orphaned objects dependencies, take 3