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)

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема 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)
Дата
Msg-id 20100430165529.GD3151@alvh.no-ip.org
обсуждение исходный текст
Ответ на 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>)
Ответы 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>)
Список 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
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 по дате отправления:

Предыдущее
От: Vincenzo Romano
Дата:
Сообщение: Re: Inheritance efficiency
Следующее
От: Glyn Astill
Дата:
Сообщение: 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)