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 71811D1B340 for ; Tue, 22 Jun 2004 11:32:20 -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 79650-05 for ; Tue, 22 Jun 2004 14:32:20 +0000 (GMT) Received: from resmta01.ono.com (smtp.ono.com [62.42.230.12]) by svr1.postgresql.org (Postfix) with ESMTP id BEEEED1B2D9 for ; Tue, 22 Jun 2004 11:32:14 -0300 (ADT) Received: from [80.58.11.235] by resmta01.ono.com with HTTP; Tue, 22 Jun 2004 16:32:18 +0200 Date: Tue, 22 Jun 2004 16:32:18 +0200 Message-ID: <40D7954B00000651@resmta01.ono.com> In-Reply-To: <20040620151209.GA12443@wolff.to> From: juanmime@ono.com Subject: Problems restoring a DB with oids To: 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/287 X-Sequence-Number: 13947 Hello, I have two servers running postgres 7.3 (Server Jupiter), and 7.4.3 (Sever Saturn), in my office. I have a master database in Jupiter, that contains a DB with images, OIDs (lo type). I'm trying to backup the database from Jupiter and restore it in Saturn. I do this, from Saturn: pg_dump -Ft -b -U dbuser -h saturn dbsample > db.tar Then, I create the user and database in Saturno, and perform this: pg_restore -Ft -v db.tar -d dbsample -U dbuser But, pg_restore stops, showing this message: pg_restore: no OID type columns in table photos1 pg_restore: fixing up large-object cross-reference for "inventory" pg_restore: no OID type columns in table inventory pg_restore: fixing up large-object cross-reference for "photos2" pg_restore: fixing large object cross-references for photos2.photo pg_restore: fixing up large-object cross-reference for "parts" pg_restore: fixing large object cross-references for parts.qltymemdoc pg_restore: [archiver (db)] error while updating column "qltymemdoc" of table "parts": ERROR: large object 609937 does not exist pg_restore: *** aborted because of error But this large object, exists. I "untar" the "db.tar" file, and there is a file called "blob_609937.dat", and it appears in the file "blobs.toc". Where is the problem ? How can I do a safety reliable backup in postgres, with databases that cont= ains "lo" columns ? I have tried with diferents options (dumping and restoring), but always appear the same problem. This have seen this problem in databases using large objects (lo type), since version 7.3. It is a critical situation, because I have seen those problems in a product= ion system, .... what will happend if the database would crack ? Thanks.