From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Dependencies for partitioned indexes are still a mess
In-reply-to: <20200812221313.zfqsfcpt2tmkv4la@alap3.anarazel.de>
References: <3170626.1594842723@sss.pgh.pa.us>
 <20200812221313.zfqsfcpt2tmkv4la@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Wed, 12 Aug 2020 15:13:13 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <324384.1597271356.1@sss.pgh.pa.us>
Date: Wed, 12 Aug 2020 18:29:16 -0400
Message-ID: <324385.1597271356@sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> I've attached the diff between first.sql and second.sql. Here's the
> highlights:

As I recall, the differences in b_star etc are expected, because
pg_dump reorders that table's columns to match its inheritance parent,
which they don't to start with because of ALTER TABLE operations.

I'm pretty sure we set it up that way deliberately ages ago, because
pg_dump used to have bugs when contending with such cases.  Not sure
about a good way to mechanize recognizing that these diffs are
expected.

Dunno about test_type_diff2, but it might be a newer instance of
the same thing.

			regards, tom lane