Bug in pg_dump/pg_restore

Started by Herbert Liechtiover 24 years ago2 messagesgeneral
Jump to latest
#1Herbert Liechti
Herbert.Liechti@thinx.ch

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 an 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 restored?

Best regards
Herbie

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Herbert Liechti http://www.thinx.ch
ThinX networked business services Adlergasse 5, CH-4500 Solothurn
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#2Doug McNaught
doug@wireboard.com
In reply to: Herbert Liechti (#1)
Re: Bug in pg_dump/pg_restore

Herbert Liechti <Herbert.Liechti@thinx.ch> writes:

Hello all

I found a bug in pg_dump / pg_restore in the Release 7.1.2.

I'm pretty sure 7.1.3 contains some pg_dump bugfixes. You might want
to upgrade.

-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863