Re: Rethinking the parameter access hooks for plpgsql's benefit

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit
Date: 2015-03-09 17:03:02
Message-ID: 20150309170302.GB22823@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-03-09 12:54:44 -0400, Robert Haas wrote:
> If we're changing that policy for patches submitted by Salesforce
> employes, I'm afraid I must object unless EnterpriseDB employees will
> get the same privilege. And I think 2ndQuadrant will want in on it,
> too.

Right. I'm not really sure how much actual policy there is around this,
and how much (differently) perceived policy it is.

> > I will admit that I'm been slacking on commitfest work. This is not
> > unrelated to the fact that we've been in commitfest mode continuously
> > since last August. I'm afraid whatever enthusiasm I had for reviewing
> > other peoples' patches burned out some time ago.
>
> Yeah, it would be so much easier to get the release out the door if
> people didn't keep submitting patches to make the product better. We
> should really try to discourage that.

I don't think that's really the point. There's been awfully little
progress on the committing side, and what did happen has been born by
few shoulders. Which leaves little time that's officially dedicated to
the fun parts.

Greetings,

Andres Freund

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2015-03-09 17:04:13 Calling for a replacement committer for GROUPING SETS
Previous Message Robert Haas 2015-03-09 16:59:48 Re: Rethinking the parameter access hooks for plpgsql's benefit