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>
Subject: Re: Problem restoring with pg_dump
Date: Sat, 02 Dec 2006 01:18:09 +0000
Message-ID: <4570D451.1070907@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...

I may end up duplicating myself here - seem to be having lots of problems with
the Postgres new server so apologies.

The data file is from a live server and has been steadily growing. It's
1.2Gbytes(ish) in size. It was built with --compress=9. Does Postgres uncompress
this to something bigger than 2Gbytes before processing and busting what can be
referenced in a 32 bit seek value? What happens (in Linux) when you try to open
a file that is bigger than 2Gbytes - do you loose the ability to seek?

I've just taken apart the schema def. from pg_dump --schema-only and inserted
the data-restore after the tables are created but before
indices/constraints/rules are replied. in this case I don't have to re-order the
tables. Restore doesn't seem to be having problems in this case - although the
restore will take a good while to complete. This is with the same dump file that
failed before.

Pete

> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
> 



view thread (10+ messages)

Message-ID: <4570D451.1070907@yellowhawk.co.uk>
Permalink:  ../4570D451.1070907@yellowhawk.co.uk/
Also on:    postgresql.org/message-id/4570D451.1070907@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: <4570D451.1070907@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> <4570D451.1070907@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