Hallo
I dumped a database with large objects with the command pg_dump -Fc -b
dbname > dbname.dmp
To restore the DB I use pg_restore -d newdb dbname.dmp.
The restore process breakes with the following error message:
pg_restore: [archiver (db)] could not execute query: ERROR: relation
"tablename"
Hallo
I try to restore a large DB with BLOBS. I created the dump file with:
pg_dump -Fc -b > dump.file
During the restore process startet with the following command:
pg_restore -d dump.file
the process breakes with the error message that a table couldn't be found.
So I started the pg_restore
Vishal
Thank you for your answer. My problem is, I have to restore BLOBS. The
documentation says, it's only possible to restore blobs with pg_restore in
one part. The way you suppose does not work with BLOBS because the
restauration of single objects will not restore BOLBS.
Horst Düster
-Urs
OK, the manual talk about this solution, but I do have more than 2000
objects in my DB. What is the reason that pg_dump/pg_restore are not able to
create an correct order ob DB objects with respect to their constraints. All
tables must be created before the views are created and so on?
Horst
---
I want to migrate a DB from PG 7.4.6 to PG 8.0.0. Thus I dumped a PG 7.4.6
DB with the command
pg_dump -Fc -h host -U user dbname > db.dmp (pg_dump Version (PostgreSQL)
8.0.0)
after the dump I create a TOC list file with
pg_restore -l db.dmp > db.lst (pg_restore Version
(Postgr
Michael
Thank you for your response.
>Are you sure reordering was necessary? Did you try to restore
>without reordering the objects?
Yes I tried the restore without reordering, but it doesn't work due to the
fact that pg_restore tries to restore some objects of my DB before it is
allowed to res
There exists a second reason to walk my way. I work with PostGIS. To update
PostGIS you need to replace different functions, operators etc. for it it
exists an update process which expect the use of a TOC list. I think the
best way is to patch this pg_restore bug
-
