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: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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-04-30 17:00:46
Message-ID: 646702.45201.qm@web23604.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

--- On Fri, 30/4/10, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> Uh.  Why are you doing that?  pg_restore is
> supposed to restore the
> schema, then data, finally indexes and other stuff. 
> Are you using
> separate schema/data dumps?  If so, don't do that --
> it's known to be
> slower.

Yes, I'm restoring the schema first, then the data.

The reason being that the data can come from different slony 1.2 slaves, but the schema always comes from the origin server due to modifications slony makes to schemas on the slaves.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-04-30 17:02:36 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)
Previous Message Alvaro Herrera 2010-04-30 16:55:29 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)