From: | John Siracusa <siracusa(at)mindspring(dot)com> |
---|---|
To: | Postgres Admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_dump/pg_restore |
Date: | 2004-01-12 16:29:52 |
Message-ID: | BC2835B0.78BAB%siracusa@mindspring.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 1/12/04 11:17 AM, Sai Hertz And Control Systems wrote:
> Dear Alexey Bobkov ,
>> Then a try to restore my data:
>> pg_restore /path_to_database/backup/db_backup.file
>> and get next error
>> pg_restore: [archiver] input file does not appear to be a valid archive
>
> Use psql instead with command
> psql -U username databasename -f yourdb_file.sql
> Yes you will have to edit the file a bit.
> Drawbacks are :
> triggers will go of on all insert and will be stumbling block
Is this true when dumping using pg_dumpall and restoring by piping to psql?
Are triggers going off during the restore? I don't see a --disable-triggers
option to pg_dumpall.
-John
From | Date | Subject | |
---|---|---|---|
Next Message | Sai Hertz And Control Systems | 2004-01-12 16:36:14 | Re: [HACKERS] IEEE 754 |
Previous Message | Sai Hertz And Control Systems | 2004-01-12 16:17:08 | Re: pg_dump/pg_restore |