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 26F6DD1EB25 for ; Tue, 6 Apr 2004 12:32:49 -0300 (ADT) 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 96126-08 for ; Tue, 6 Apr 2004 12:32:47 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 06C76D1EA92 for ; Tue, 6 Apr 2004 12:32:47 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i36FWkcW025099; Tue, 6 Apr 2004 11:32:46 -0400 (EDT) To: "Marion McKelvie" Cc: pgsql-admin@postgresql.org Subject: Re: restoring large objects In-reply-to: References: Comments: In-reply-to "Marion McKelvie" message dated "Tue, 06 Apr 2004 13:02:35 +0100" Date: Tue, 06 Apr 2004 11:32:46 -0400 Message-ID: <25098.1081265566@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/89 X-Sequence-Number: 13062 "Marion McKelvie" writes: > I am running with 7.1.2 (I know it's old, but I don't have a lot of choice > given the application running on it), and have dumped the database with > the -b option. However, the restoration process generates new ids for the > large objects which means the link between the data table referencing them > and the content of pg_largeobject is lost. pg_dump includes code in the dump that is supposed to update references to match the new large object OIDs. Check into why that didn't work for you. (One fairly likely possibility is that you stored the references in the wrong type of column --- it has to be type "oid" or "lo" or pg_dump won't think it needs updating.) regards, tom lane