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 F1D27528C6 for ; Wed, 15 Jun 2005 00:56:26 -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 73530-01 for ; Wed, 15 Jun 2005 03:56:16 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9475952889 for ; Wed, 15 Jun 2005 00:56:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j5F3rt1u027811; Tue, 14 Jun 2005 23:53:55 -0400 (EDT) To: "Amrit Angsusingh" Cc: postgresql admin Subject: Re: Blob error after backup and restore [database > 5.5 Gb.] In-reply-to: <20050615030013.2346.qmail@chaiyo.com> References: <20050615030013.2346.qmail@chaiyo.com> Comments: In-reply-to "Amrit Angsusingh" message dated "15 Jun 2005 03:00:13 -0000" Date: Tue, 14 Jun 2005 23:53:55 -0400 Message-ID: <27810.1118807635@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/98 X-Sequence-Number: 17853 "Amrit Angsusingh" writes: > after I try to restore it in another server which has the same environment [via nfs] and use the command > pg_restore -d test test.tar > The database "test" after restoration has the same data but no blob > found . Another thought here: what exactly do you mean by "no blob found"? The current implementation does not try to restore blobs with the same OIDs they had in the original database --- rather, it loads them up with whatever OIDs the new backend cares to assign, and then tries to fix up database columns of OID and LO types to reference the new OIDs instead of the old ones. This is obviously pretty fragile, and we are thinking about changing it for 8.1, but I wonder if you are getting bit because you are doing something that pg_restore isn't expecting. regards, tom lane