| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dump, restore, dump yields differences |
| Date: | 2013-03-22 19:54:23 |
| Message-ID: | CAM-w4HPP=Xqs80wxEkgrBGMLJ3O2R1C3DxYaDK5bMEWhW+9rjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2013 at 6:49 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-22 19:55:08 | Re: Default connection parameters for postgres_fdw and dblink |
| Previous Message | Tom Lane | 2013-03-22 19:52:05 | Re: Page replacement algorithm in buffer cache |