| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: crash with sql language partition support function |
| Date: | 2018-04-12 16:09:53 |
| Message-ID: | CA+TgmoYk_fHkqo1055djygxqFfd3Ju2e3swRMSEZ3UZC0NwTmQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 12, 2018 at 8:55 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-04-12 16:17:57 | Re: Native partitioning tablespace inheritance |
| Previous Message | Alvaro Herrera | 2018-04-12 16:05:22 | Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour. |