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

From Peter Geoghegan
Subject Re: Rethinking the parameter access hooks for plpgsql's benefit
Date
Msg-id CAM3SWZRod=irduFu=HE5oqducAROXLEfndpgpd=x4qcWYMTY8A@mail.gmail.com
Whole thread Raw
In response to Re: Rethinking the parameter access hooks for plpgsql's benefit  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Wed, Mar 18, 2015 at 10:26 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2015-03-18 13:12:11 -0400, Tom Lane wrote:
>> Indeed.  In this case, since the patch in question is one that
>> improves/simplifies a patch that's already in the current commitfest,
>> I'm going to go ahead and push it.  If you want to call a vote on
>> revoking my commit bit, go right ahead.
>
> 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.

+1


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: Can pg_dump make use of CURRENT/SESSION_USER