X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B050CD1B191 for ; Wed, 23 Jun 2004 08:43:33 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 49342-02 for ; Wed, 23 Jun 2004 11:43:34 +0000 (GMT) Received: from mta02.onolab.com (smtp.ono.com [62.42.230.12]) by svr1.postgresql.org (Postfix) with ESMTP id D283AD1BAA0 for ; Wed, 23 Jun 2004 08:43:30 -0300 (ADT) Received: from [80.58.11.235] by mta02.onolab.com with HTTP; Wed, 23 Jun 2004 13:43:25 +0200 Date: Wed, 23 Jun 2004 13:43:25 +0200 Message-ID: <40D794F2000011E9@mta02.ono.com> In-Reply-To: <19514.1087924535@sss.pgh.pa.us> From: juanmime@ono.com Subject: Asunto: Re: Problems restoring a DB with oids To: "Tom Lane" Cc: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200406/304 X-Sequence-Number: 13964 Thanks you very much Tom, Here is the solution to the problem: First: We have to restore (only) the structure (schema) of the database pg_restore -Ft -v -s db.tar -d database_name -U postgres -S postgres --disa= ble-triggers Second: Restore the datas pg_restore -Ft -v -a db.tar -d database_name -U postgres -S postgres --disa= ble-triggers I think, that in the first step, we can drop "-S postgres --disable-trigger= s" options. Thanks.