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 82F55D1E0D2 for ; Wed, 18 Feb 2004 16:57:50 +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 94851-07 for ; Wed, 18 Feb 2004 12:57:48 -0400 (AST) Received: from mail.securitylending.com (mail.securitylending.com [65.90.55.69]) by svr1.postgresql.org (Postfix) with ESMTP id 0CF30D1E0EF for ; Wed, 18 Feb 2004 12:57:46 -0400 (AST) Subject: Re: HELP - need way to restore only blobs From: Warren Little To: Jeff Boes Cc: pgsql-admin@postgresql.org In-Reply-To: References: <1077046844.5869.25.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1077123449.5903.0.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 18 Feb 2004 09:57:29 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/269 X-Sequence-Number: 12443 Thanks to all who responded. Found the pg_dumplo tool in contrib which did exactly what I needed. On Wed, 2004-02-18 at 05:54, Jeff Boes wrote: > At some point in time, wlittle@securitylending.com (Warren Little) wrote: > > >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. > > In a similar situation, we wrote a script that constructs "\lo_export" commands > to dump each large object to a file. The file name for each contains the > information needed to reconstruct the object at the other end. For instance, if > you have a table like this: > > CREATE TABLE foobar (primary_id INTEGER PRIMARY KEY, large_obj OID, ...) > > you'd want a series of commands that look like this: > > \lo_export .dmp > > Then, given a directory full of such files, you construct another series of > commands that look like this: > > \lo_import .dmp > > UPDATE foobar SET large_obj = WHERE primary_id = ; > > The trick is capturing the output of the \lo_import command and parsing it to > get the large object OID after it is created. > > I don't know if I have permission to post or email the script, but if you > contact me offline I should know by then. > > jboes at n/e/x/c/e/r/p/t/d/o/t/c/o/m > > -- > ~~~~~~~~~~~~~~~~| Genius may have its limitations, but stupidity is not > Jeff Boes | thus handicapped. > jboes@qtm.net | --Elbert Hubbard (1856-1915), American author > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly -- Warren Little Senior Vice President Secondary Marketing Security Lending Wholesale, LC www.securitylending.com Tel: 866-369-7763 Fax: 866-849-8082