X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E5F44D1B461 for ; Mon, 12 Jan 2004 16:30:35 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 99562-04 for ; Mon, 12 Jan 2004 12:30:05 -0400 (AST) Received: from cayenne.palmdigitalmedia.com (cayenne.palmdigitalmedia.com [63.110.43.230]) by svr1.postgresql.org (Postfix) with SMTP id 8F648D1DA98 for ; Mon, 12 Jan 2004 12:30:04 -0400 (AST) Received: (qmail 32164 invoked from network); 12 Jan 2004 16:29:58 -0000 Received: from unknown (HELO ?192.168.124.23?) (63.110.43.226) by 0 with SMTP; 12 Jan 2004 16:29:58 -0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 12 Jan 2004 11:29:52 -0500 Subject: Re: pg_dump/pg_restore From: John Siracusa To: Postgres Admin Message-ID: In-Reply-To: <4002C884.3080000@sancharnet.in> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/89 X-Sequence-Number: 11952 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