Re: pg_dump is broken for partition tablespaces

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: pg_dump is broken for partition tablespaces
Date: 2019-03-06 14:36:07
Message-ID: 16497.1551882967@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> As far as I can see, the biggest fundamental difference with doing
> things this way will be that the column order of partitions will be
> preserved, where before it would inherit the order of the partitioned
> table. I'm a little unsure if doing this column reordering was an
> intended side-effect or not.

Well, if the normal behavior results in changing the column order,
it'd be necessary to do things differently in --binary-upgrade mode
anyway, because there we *must* preserve column order. I don't know
if what you're describing represents a separate bug for pg_upgrade runs,
but it might. Is there any test case for the situation left behind by
the core regression tests?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tushar 2019-03-06 14:37:24 Server Crash in logical decoding if used inside --single mode
Previous Message Paul Guo 2019-03-06 14:06:27 Batch insert in CTAS/MatView code