Re: crash with sql language partition support function - Mailing list pgsql-hackers

From Robert Haas
Subject Re: crash with sql language partition support function
Date
Msg-id CA+TgmoYk_fHkqo1055djygxqFfd3Ju2e3swRMSEZ3UZC0NwTmQ@mail.gmail.com
Whole thread Raw
In response to Re: crash with sql language partition support function  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: crash with sql language partition support function
List pgsql-hackers
On Thu, Apr 12, 2018 at 8:55 AM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Amit Langote wrote:
>> Anyway, after reading your replies, I thought of taking a stab at unifying
>> the partitioning information that's cached by relcache.c.
>
> Wow.  Now that's one large patch.  I'm going to run with this for HEAD,
> but I think we should do a minimal fix for PG10.

Is there really a compelling reason to do more than minimal fixes in
HEAD?  We are (or should be) trying to stabilize this branch so we can
ship it and start the next one, and the chances that heavy hacking on
this will delay that process seem better than average.

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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour.
Next
From: Robert Haas
Date:
Subject: Re: Native partitioning tablespace inheritance