| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(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 19:58:50 |
| Message-ID: | 20180412195850.75wkxk2ynbtd45ir@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Keith Fiske wrote:
> I'm also not sure that we should have this mindset of partitioning working
> as inheritance does either. Inheritance was only used before because it was
> the only mechanism available. And while you do still use it under the hood
> for parts of partitioning, I don't see any reason we should be let people
> assume that partitioning works anything like inheritance.
+1 (See also ALTER TABLE .. SET OWNER, which I ought to have fixed but
didn't).
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-12 19:59:05 | Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour. |
| Previous Message | Keith Fiske | 2018-04-12 19:55:57 | Re: Native partitioning tablespace inheritance |