Re: dump, restore, dump yields differences

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: dump, restore, dump yields differences
Date: 2013-03-22 18:49:15
Message-ID: 26569.1363978155@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> As part of testing the matview issues around dumping, I ran `make
> installcheck-world`, ran pg_dump to dump the regression database,
> loaded it into a new database, dumped the newly restored database,
> and compared the output files from the two pg_dump runs. There
> were a few somewhat surprising differences, attached. Do we want
> to worry about these, or leave them alone?

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-03-22 19:05:56 Re: Page replacement algorithm in buffer cache
Previous Message Kevin Grittner 2013-03-22 18:41:48 dump, restore, dump yields differences