Re: Rethinking the parameter access hooks for plpgsql's benefit - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Rethinking the parameter access hooks for plpgsql's benefit
Date
Msg-id 20150318183313.GA26995@alap3.anarazel.de
Whole thread Raw
In response to Re: Rethinking the parameter access hooks for plpgsql's benefit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2015-03-18 14:01:41 -0400, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > Seriously? In my opinion it has to be possible to doubt whether a patch
> > should be committed in certain release without it being interpreted as a
> > personal attack.
> 
> I don't think anyone's said anything in this thread that amounts to a
> personal attack.

From where I am sitting you appear somewhat offended. If not, great.

> If someone's going to tell me that my judgment about when to push
> something is not acceptable, then they probably ought to be calling
> for removal of my commit privileges.

I think this is making the issue far bigger than it is. I think every
committer and most contributors in this project have swallowed more
decisions they didn't agree with than they care to count. And that's
normal. Let's try to keep it a bit more low key.

> We have a difference of opinion on policy, and what I'm saying is that
> the policy ultimately reduces to trusting individual committers to use
> their best judgment.

I think the issue is much less, if at all, about trusting committers,
than about a different view about how to hanlde our problems with
release management. Quite apparently 9.4 didn't work out greatly, which
probably excerbates preexisting (perhaps unknowingly so) differences in
opinion about until when new patches should be "allowed".

There's also the problem, as you noted, that we're all fucking tired of
neverending 2014-06 commitfest. Robert is, apparently at least, of the
opinion that that's best handled by stopping to accept new patches and
trying reduce the size of the backlog. That doesn't sound entirely
unreasonable. It also doesn't sound unreasonable to deal with that
backlog by doing the stuff oneself deems important.  I personally am
*really* worried about the current state; without having a short/mid
term solution. I think this makes postgres really unattractive to
contribute to. And that has, and will, cost us a lot of help.


Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Install shared libs in lib/ and bin/ with MSVC (Was: install libpq.dll in bin directory on Windows / Cygwin)
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: Can pg_dump make use of CURRENT/SESSION_USER