Postgres Pro
Downloads
Home   >   mailing lists

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) - Mailing list pgsql-general

From Alvaro Herrera
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
Msg-id 20100430165529.GD3151@alvh.no-ip.org
Whole thread Raw
In response to 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)  (Glyn Astill <glynastill@yahoo.co.uk>)
Responses 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)
List pgsql-general
Tree view 
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
schemaand 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.

pgsql-general by date:

Previous
From: Vincenzo Romano
Date:
Subject: Re: Inheritance efficiency
Next
From: Glyn Astill
Date:
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)