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: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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-04-30 16:55:29
Message-ID: 20100430165529.GD3151@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Glyn Astill wrote:

> One thing I forgot to mention is that in the restore script I drop the indexes off my tables between restoring the schema and the data. I've always done this to speed up the restore, but is there any chance this could be causing the issue?

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.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Glyn Astill 2010-04-30 17:00:46 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 Mario Wojcik 2010-04-30 16:53:02 Re: Nuevo sobre PGday Latinoamericano 2011...