| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Small bug in pg_dump |
| Date: | 2001-03-19 14:59:03 |
| Message-ID: | 200103191459.JAA09170@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This does make me wonder (again) about some kind of pg_dump regression
> test. ISTM that a test should be doable by building a DB from data files,
> dumping it, restoring it, then using COPY to extract the data back to files
> (and probably doing a sort on the output). We could also store a BLOB or
> two. Then we compare the initial data files with the final ones. This will
> test the integrity of the data & BLOB dump/restore. We then also need to
> test the metadata integrity somehow, probably by dumping & restoring the
> regression DB, but we'd need to modify the pg_dump output somewhat, I think.
Yes, I have often caught dump bugs by doing a COPY/restore/COPY and
comparing the two COPY files. Not sure if that is what you meant.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Renters | 2001-03-19 15:40:56 | Re: beta6 pg_restore core dumps |
| Previous Message | Oleg Bartunov | 2001-03-19 14:42:43 | New version of contrib-intarray is ready ! |