Re: pg_restore: [custom archiver] dumping a specific TOC data block out of order is not supported without ID on this input stream (fseek required)

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_restore: [custom archiver] dumping a specific TOC data block out of order is not supported without ID on this input stream (fseek required)
Date: 2010-05-21 12:20:12
Message-ID: 8CC453FD-4DC9-4955-A3A8-C9762F80C54E@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 21 May 2010, at 12:44, Glyn Astill wrote:

>> So I guess your large object is too large.
>
> Hmm, we don't use any large objects though, all our data is pretty much just date, text and numeric fields etc

Doh! Seems I mixed up a few threads here. It was probably the mentioning of a 5GB file that threw me off, hadn't realised you were referring to a dump file there.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.

!DSPAM:737,4bf67a7e10411591919641!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Smith 2010-05-21 13:31:40 Re: How feasible is this?
Previous Message Sam Mason 2010-05-21 11:40:40 Re: How to lose transaction history (xmin values, WAL, etc.)?