From: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Native partitioning tablespace inheritance |
Date: | 2018-04-12 18:40:54 |
Message-ID: | CADA5465-60CB-4CBC-9A54-38E346273924@excoventures.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Apr 12, 2018, at 2:36 PM, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>> On Apr 12, 2018, at 09:17, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Hmm, that's interesting. So you want the children to inherit the
>> parent's tablespace when they are created, but if the parent's
>> tablespace is later changed, the existing children don't move?
>
> +1 to that behavior.
>
> While it's always possible to just say "do the right thing" to the application when creating new children (that is, expect that they will always specify a tablespace if it's not the default), this seems like the least-surprising behavior.
>
> It's true that an unpartitioned table will always be created in the default tablespace unless otherwise specified, but child tables are sufficiently distinct from that case that I don't see it as a painful asymmetry.
If there are no strong objections I am going to add this to the “Older Bugs”
section of Open Items in a little bit.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2018-04-12 18:47:25 | wal_consistency_checking reports an inconsistency on master branch |
Previous Message | Andrew Gierth | 2018-04-12 18:37:21 | Re: submake-errcodes |