From: | Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Problem restoring with pg_dump |
Date: | 2006-11-28 10:00:37 |
Message-ID: | ekh1c7$1qct$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I posted this to 'general' yesterday but with no luck. This is probably a better
group.
I've just got the following message while trying to restore a database :
pg_restore : [custom archiver] Dumping a specific TOC data block out of order is
not supported without ID on this input stream (fseek required).
The command was :
pg_restore -L /tmp/toc --dbname=whitebeam --disable-triggers --username=postgres
/var/backups/restore-db.psql
/tmp/toc is a re-orderd output from :
pg_restore -l -a /var/backups/restore-db.psql > /tmp/toc
Using Postgres 8.1.4 on
Linux version 2.6.15-1.2054_FC5
The dump itself was made on another machine running 8.1.4 on Fedora core 4.
I've run similar commands on this machine before with no problems. Not sure why
I should start to have these problems now?
Anyone else seen anything similar? Thoughts much appreciated!
Pete
From | Date | Subject | |
---|---|---|---|
Next Message | Jessica Richard | 2006-11-28 11:34:53 | how do I create a db with unicode encoding on a utf8 server |
Previous Message | Marcelo Costa | 2006-11-27 16:36:41 | Re: Drop All Index |