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 20150318172653.GN27420@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>)
Responses Re: Rethinking the parameter access hooks for plpgsql's benefit
Re: Rethinking the parameter access hooks for plpgsql's benefit
List pgsql-hackers
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.

Greetings,

Andres Freund

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Can pg_dump make use of CURRENT/SESSION_USER
Next
From: Peter Geoghegan
Date:
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit