From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: behaviour change - default_tablesapce + partition table |
Date: | 2019-06-06 22:52:24 |
Message-ID: | 20190606225224.GA8363@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-May-20, Alvaro Herrera wrote:
> On 2019-May-20, Amit Langote wrote:
>
> > Should we add this to open items?
>
> Yeah. I'm AFK this week, but can handle it afterwards. The fix already
> missed beta1, so I don't think there's a problem with taking a little
> bit longer.
Here's my proposed patch. I changed/expanded the tests a little bit to
ensure more complete coverage.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
tablespace-partitioned.patch | text/x-diff | 6.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-06-06 23:02:42 | Re: behaviour change - default_tablesapce + partition table |
Previous Message | Goel, Dhruv | 2019-06-06 22:13:14 | Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY |