X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3CBD7D1D8DA for ; Tue, 17 Feb 2004 19:40:51 +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 98921-09 for ; Tue, 17 Feb 2004 15:40:45 -0400 (AST) Received: from mail.securitylending.com (mail.securitylending.com [65.90.55.69]) by svr1.postgresql.org (Postfix) with ESMTP id EEB00D1B49E for ; Tue, 17 Feb 2004 15:40:43 -0400 (AST) Subject: HELP - need way to restore only blobs From: Warren Little To: pgsql-admin@postgresql.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1077046844.5869.25.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 17 Feb 2004 12:40:44 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/261 X-Sequence-Number: 12435 I recently posted a similar message but left some key info out: I migrated my database from 7.3 to 7.4 this weekend using the pg_dumpall tool which I now realize does not capture blobs. I now need to move only the blob data to the 7.4 database. The problem with redoing the dump with pg_dump -b is the database is now in production and writing over the top of changes to the database is not exceptable. The blob data is very static so if there was some way to copy the physical files from disk and modify some records in the system tables to properly locate the blob records that would be best. Another option I was looking at was to restore the archived database with the blobs intact and then restore the production version over the top without destroying the blob data. All suggestions welcome, I'm dying here. -- Warren Little Senior Vice President Secondary Marketing Security Lending Wholesale, LC www.securitylending.com Tel: 866-369-7763 Fax: 866-849-8082