X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4E7F6D834D for ; Thu, 8 Sep 2005 10:37:21 -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 94763-10 for ; Thu, 8 Sep 2005 13:37:16 +0000 (GMT) Received: from mx1.surnet.cl (mx2.surnet.cl [216.155.73.181]) by svr1.postgresql.org (Postfix) with ESMTP id 087CDD7FE5 for ; Thu, 8 Sep 2005 10:37:15 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx1.surnet.cl with ESMTP; 08 Sep 2005 09:37:08 -0400 X-IronPort-AV: i="3.96,179,1122868800"; d="scan'208"; a="6650647:sNHT30862896" Received: from alvh.no-ip.org (216.155.85.134) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 4317C634000BDD4F; Thu, 8 Sep 2005 09:37:19 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id D24DAC2DC74; Thu, 8 Sep 2005 09:38:17 -0400 (CLT) Date: Thu, 8 Sep 2005 09:38:17 -0400 From: Alvaro Herrera To: Adam Witney Cc: Tom Lane , pgsql-admin , Michael Fuhr Subject: Re: pg_dump error... Follow up Message-ID: <20050908133817.GD12971@surnet.cl> Mail-Followup-To: Adam Witney , Tom Lane , pgsql-admin , Michael Fuhr References: <28274.1126113140@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.343 required=5 tests=[AWL=-0.483, DNS_FROM_RFC_ABUSE=0.374, DNS_FROM_RFC_POST=1.376, FORGED_RCVD_HELO=0.05, RCVD_IN_NJABL_PROXY=1.026] X-Spam-Level: ** X-Archive-Number: 200509/76 X-Sequence-Number: 18813 On Thu, Sep 08, 2005 at 10:32:41AM +0100, Adam Witney wrote: > Unfortunately the pg_filedump you requested gives an error: > > pg_filedump -R 165390 165392 134401986 > > ******************************************************************* > * PostgreSQL File/Block Formatted Dump Utility - Version 3.0 > * > * File: 134401986.1 > * Options used: -R 165390 165392 > * > * Dump created on: Thu Sep 8 10:33:47 2005 > ******************************************************************* > Error: Premature end of file encountered. > > (there is a .1 file also for this table, do I have to stick the two together > or something?) No, rather tell pg_filedump to use the second segment (.1 file) and substract the total number of blocks in the first segment. If my math is right there are 131072 blocks of 8kB per 1GB segment, so to dump block 165390 you need to ask for block 34318 in the second segment: pg_filedump -R 34318 34320 134401986.1 -- Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com "Et put se mouve" (Galileo Galilei)