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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 16:29:58
Message-ID: CA+TgmoZPNJmP7u_ZB3y33nDqgJrekTfVG6CdtnGvSmfoxHZc-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 9, 2015 at 12:26 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> From the reading the original post it seems like the patch was developed on
> Sales Force's time, not TGLs. I do not think we get to have an opinion on
> that.

Salesforce gets to develop their patches whenever they want, but they
don't get to control the community process for getting those patches
committed to PostgreSQL.

> Thank you Tom for the efforts you made here, making the largest used PL
> better, faster, stronger is exactly the type of micro-changes we need to be
> looking at for further polish within the database.

So, just to be clear, are you proposing that everybody is exempted
from the CommitFest deadlines, or just Tom?

Thanks,

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-03-09 16:31:25 Re: Bootstrap DATA is a pita
Previous Message Joshua D. Drake 2015-03-09 16:26:04 Re: Rethinking the parameter access hooks for plpgsql's benefit