Re: Bug in pg_dump/pg_restore

Hi Herbie,

my advice to have secure backups ist to upgrade to 7.1.3. AFAIK there are
some minor bugs in pg_dump on 7.1.2. But i've never heard of losing tables.
The only problem I've come across, was tha wrong definition of views. So I
had to define all my views anew. But no data were lost.
I use pg_dump without any special options and then restore via psql -i
mydb.dmp after I have droped an recreated the database itself.

Andre

<Herbert(dot)Liechti(at)thinx(dot)ch> schrieb im Newsbeitrag
news:Pine(dot)LNX(dot)4(dot)33(dot)0110192108220(dot)24135-100000(at)standbyme(dot)thinx(dot)ch(dot)(dot)(dot)
>
> Hello all
>
> I found a bug in pg_dump / pg_restore in the Release 7.1.2. I tried to
> restore a database which was dumped with the following arguments:
>
> pg_dump --blob -Fc mydb -f /home/backup/mydb.dump
>
> Today I tried to restore the backup for testing purposes on an other
> machine. The pg_restore complained about a table that does not exist. A
> good thing that this was just a test. After recreating the table and
> reloading the data in the newly created table the pg_dump/pg_restore
> utility was working correctly again. A few days ago we added a additional
> boolean attribute to that table with the alter table statement.
>
> So, what is your advice to have secure backups? Is there a possiblity to
> check wether a backup can properly be restored?
>
> Best regards
> Herbie
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Herbert Liechti http://www.thinx.ch
> ThinX networked business services Adlergasse 5, CH-4500 Solothurn
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html