Re: pg_dump is broken for partition tablespaces - Mailing list pgsql-hackers

From David Rowley
Subject Re: pg_dump is broken for partition tablespaces
Date
Msg-id CAKJS1f9k0Jnaf3mEZZrTN8SfANcOprN6YmF+U3TZMFBSYU1QuA@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump is broken for partition tablespaces  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: pg_dump is broken for partition tablespaces
List pgsql-hackers
On Tue, 23 Apr 2019 at 18:18, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> If partitions needed a
> map in the old database, this patch means that they will *continue* to
> need it in the new database.

That's incorrect.  My point was about dropped columns being removed
after a dump / reload.  Only binary upgrade mode preserves
pg_attribute entries for dropped columns. Normal mode does not, so the
maps won't be needed after the reload if they were previously only
needed due to dropped columns.  This is the case both with and without
the pg_dump changes I proposed.  The case the patch does change is if
the columns were actually out of order, which I saw as an unlikely
thing to happen in the real world.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Regression test PANICs with master-standby setup on samemachine
Next
From: Masahiko Sawada
Date:
Subject: Re: New vacuum option to do only freezing