Re: Parallel safety tagging of extension functions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel safety tagging of extension functions
Date: 2016-05-21 03:45:21
Message-ID: CAB7nPqSCnMf31cJt4E4ixNbFci0E1amuQZ3DE39K=Okavvxndg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 20, 2016 at 10:30 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 5/20/16 7:37 PM, Robert Haas wrote:
>>
>> I guess my first question is whether we have consensus on the release
>> into which we should put this. Some people (Noah, among others)
>> thought it should wait because we're after feature freeze, while
>> others thought we should do it now. If we're going to try to get this
>> into 9.6, I'll work on reviewing this sooner rather than later, but if
>> we're not going to do that I'm going to postpone dealing with it until
>> after we branch.
>
>
> Sounds to me that this is part of the cleanup of a 9.6 feature and should be
> in that release.

Yes, I agree. By the way, the patch completely ignores the fact that
some of the modules already had a version bump in the 9.6 development
cycle, like pageinpect. You don't need to create a new version script
in such cases.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hao Lee 2016-05-21 07:18:11 Does "explain (QueryTree [RAW| ANAYLZE|REWRITE] | Optimization [PULL_UP_BEFORE| PULL_UP_AFTER|...]) SELECT XXXX" helpful?
Previous Message Peter Eisentraut 2016-05-21 02:30:54 Re: Parallel safety tagging of extension functions