Re: dump, restore, dump yields differences - Mailing list pgsql-hackers

From Greg Stark
Subject Re: dump, restore, dump yields differences
Date
Msg-id CAM-w4HPP=Xqs80wxEkgrBGMLJ3O2R1C3DxYaDK5bMEWhW+9rjQ@mail.gmail.com
Whole thread Raw
In response to Re: dump, restore, dump yields differences  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Mar 22, 2013 at 6:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Those are expected.  You can trace the ALTER TABLE history of those
> tables if you want to see why they're so odd, but basically there
> are inheritance situations where it's hard to avoid this.

Incidentally it would still be cool to have make check do this dance
and intelligently compare the before and after. There have been more
than one patch where you've caught omissions in pg_dump before
applying.


-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Page replacement algorithm in buffer cache
Next
From: Tom Lane
Date:
Subject: Re: Default connection parameters for postgres_fdw and dblink