From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |
Date: | 2017-04-10 02:10:47 |
Message-ID: | 7227.1491790247@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I would appreciate help from other contributors and committers on this
> open item; pg_dump is not my strong point. In the absence of such
> help, I will do my best with it. I will set aside time this week to
> study this and send another update no later than Thursday.
The proposed patch seems rather ad-hoc, and I think that it is working
around a backend behavior that might be broken.
While I admit that I've not been paying close attention to the whole
table partitioning business, I wonder whether we have any clearly written
down specification about (a) how much partition member tables are allowed
to deviate schema-wise from their parent, and (b) how DDL semantics on
partitioned tables differ from DDL semantics for traditional inheritance.
Obviously those are closely related questions. But the fact that this
bug exists at all shows that there's been some lack of clarity on (b),
and so I wonder whether we have any clarity on (a) either.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-04-10 02:16:15 | Re: SUBSCRIPTIONS and pg_upgrade |
Previous Message | Bruce Momjian | 2017-04-10 02:06:49 | Re: [pgsql-www] Small issue in online devel documentation build |