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:59:48
Message-ID: CA+TgmoZ97pjqQNn+yaS2Th=Eo8+YVOBFC9OsK5QbTUWs3GtsnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 9, 2015 at 12:53 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> I think it is ridiculous to post on the bad/good/timing of a patch
> submission unless there is a case being made that the process isn't actually
> being followed. I don't see that here.

The CommitFest deadline was three weeks ago and I think it's
abundantly clear that Tom is not submitting this for the June
CommitFest. If that wasn't clear from his initial post, his follow-up
points have removed any doubt on that point.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-03-09 17:03:02 Re: Rethinking the parameter access hooks for plpgsql's benefit
Previous Message Robert Haas 2015-03-09 16:54:44 Re: Rethinking the parameter access hooks for plpgsql's benefit