Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 49E9B9FA136 for ; Fri, 1 Dec 2006 20:30:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 77325-02 for ; Fri, 1 Dec 2006 20:30:47 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mtaout03-winn.ispmail.ntl.com (mtaout03-winn.ispmail.ntl.com [81.103.221.49]) by postgresql.org (Postfix) with ESMTP id 0C95C9F942F for ; Fri, 1 Dec 2006 20:30:50 -0400 (AST) Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20061202003131.ROZI1865.mtaout03-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com>; Sat, 2 Dec 2006 00:31:31 +0000 Received: from [127.0.0.1] (really [82.15.227.37]) by aamtaout01-winn.ispmail.ntl.com with ESMTP id <20061202003133.VFVU219.aamtaout01-winn.ispmail.ntl.com@[127.0.0.1]>; Sat, 2 Dec 2006 00:31:33 +0000 Message-ID: <4570C933.5090300@yellowhawk.co.uk> Date: Sat, 02 Dec 2006 00:30:43 +0000 From: Peter Wilson Reply-To: petew@yellowhawk.co.uk Organization: YellowHawk Ltd User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Tom Lane CC: Peter Wilson , pgsql-admin@postgresql.org Subject: Re: Problem restoring with pg_dump References: <6113.1164728816@sss.pgh.pa.us> <1693.1165001565@sss.pgh.pa.us> In-Reply-To: <1693.1165001565@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/alternative; boundary="------------020901060003050503080907" X-Antivirus: avast! (VPS 0652-6, 01/12/2006), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/14 X-Sequence-Number: 23806 This is a multi-part message in MIME format. --------------020901060003050503080907 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Tom Lane wrote: > Peter Wilson writes: > >> Tom Lane wrote: >> >>> Could you show us the unmodified output from pg_restore -l, as well as >>> the edits you made to produce the -L script? >>> > > >> Raw output from pg_restore -l is as follows: >> > > Hm, this shows only data entries. Was the original pg_dump made with -a, > or did you use -a in the pg_restore -l command? If the latter, could we > see the full -l output? I didn't have any luck trying to reproduce this > behavior, so I'm supposing it depends on something you haven't shown us... > The dump was data-only : pg_dump -data-only -U user --format=c --compress=9 whitebeam I have a script that builds the empty database on the restore machine then fills it from the pg_dump file. This approach has worked perfectly for a year or so. Partly the question might be 'what does the error message mean?' - it almost looks like do_restore doesn't think it has a real file underneath it, instead something that only provides sequential access. I installed from RPMs. Since I originally posted I've tried the following : + installed the 8.1.5 RPMs - same result + build 8.1.5 from source - same result + run pg_restore from another machine - connecting to the server having problems - same result + Tried in a different machine - same result To make sure there isn't a difference between the database structures I've now done a pg_dump --schema-only --format=p and then used that to create the database before importing the data. Same result again. The data file itself is just about 1.2 Gbytes in size. Tonights backup I'm going to remove the --data-only to see whether I have any more luck. > regards, tom lane > Thanks Pete -- ------------------------------------------------------------------------ Peter Wilson T: 01414 160505 M: 07796 656566 http://www.yellowhawk.co.uk The information in this email is confidential and is intended for the addressee/s only. Access to this email by anyone else is unauthorised. If you are not the intended recipient, you must not read, use or disseminate the information contained in or attached to this email. -- ------------------------------------------------------------------------ Peter Wilson T: 01414 160505 M: 07796 656566 http://www.yellowhawk.co.uk The information in this email is confidential and is intended for the addressee/s only. Access to this email by anyone else is unauthorised. If you are not the intended recipient, you must not read, use or disseminate the information contained in or attached to this email. --------------020901060003050503080907 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Tom Lane wrote:
Peter Wilson <petew@yellowhawk.co.uk> writes:
  
Tom Lane wrote:
    
Could you show us the unmodified output from pg_restore -l, as well as
the edits you made to produce the -L script?
      

  
Raw output from pg_restore -l is as follows:
    

Hm, this shows only data entries.  Was the original pg_dump made with -a,
or did you use -a in the pg_restore -l command?  If the latter, could we
see the full -l output?  I didn't have any luck trying to reproduce this
behavior, so I'm supposing it depends on something you haven't shown us...
  
The dump was data-only :
    pg_dump -data-only -U user --format=c --compress=9 whitebeam

I have a script that builds the empty database on the restore machine then fills it from the pg_dump file.

This approach has worked perfectly for a year or so.

Partly the question might be 'what does the error message mean?' - it almost looks like do_restore doesn't think it has a real file underneath it, instead something that only provides sequential access.

I installed from RPMs. Since I originally posted I've tried the following :
+  installed the 8.1.5 RPMs - same result
+  build 8.1.5 from source - same result
+  run pg_restore from another machine - connecting to the server having problems - same result
+ Tried in a different machine - same result

To make sure there isn't a difference between the database structures I've now done a pg_dump --schema-only --format=p and then used that to create the database before importing the data. Same result again. The data file itself is just about 1.2 Gbytes in size.

Tonights backup I'm going to remove the --data-only to see whether I have any more luck.
			regards, tom lane
  
Thanks
Pete



--

Peter Wilson
T: 01414 160505
M: 07796 656566
http://www.yellowhawk.co.uk
The information in this email is confidential and is intended for the addressee/s only. Access to this email by anyone else is unauthorised. If you are not the intended recipient, you must not read, use or disseminate the information contained in or attached to this email.

--

Peter Wilson
T: 01414 160505
M: 07796 656566
http://www.yellowhawk.co.uk
The information in this email is confidential and is intended for the addressee/s only. Access to this email by anyone else is unauthorised. If you are not the intended recipient, you must not read, use or disseminate the information contained in or attached to this email.
--------------020901060003050503080907--