pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Wilson <petew@yellowhawk.co.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Wilson <petew@yellowhawk.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problem restoring with pg_dump
Date: Sat, 02 Dec 2006 00:30:43 +0000
Message-ID: <4570C933.5090300@yellowhawk.co.uk> (raw)
In-Reply-To: <1693.1165001565@sss.pgh.pa.us>
References: <ekh1c7$1qct$1@news.hub.org>
	<6113.1164728816@sss.pgh.pa.us>
	<ekigsd$2150$1@news.hub.org>
	<1693.1165001565@sss.pgh.pa.us>

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.

view thread (10+ messages)  latest in thread

Message-ID: <4570C933.5090300@yellowhawk.co.uk>
Permalink:  ../4570C933.5090300@yellowhawk.co.uk/
Also on:    postgresql.org/message-id/4570C933.5090300@yellowhawk.co.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: petew@yellowhawk.co.uk, tgl@sss.pgh.pa.us
  Subject: Re: Problem restoring with pg_dump
  In-Reply-To: <4570C933.5090300@yellowhawk.co.uk>
  References: <ekh1c7$1qct$1@news.hub.org> <6113.1164728816@sss.pgh.pa.us> <ekigsd$2150$1@news.hub.org> <1693.1165001565@sss.pgh.pa.us> <4570C933.5090300@yellowhawk.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox