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)

--- On Fri, 30/4/10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
> writes:
> > I've just upgraded a server from 8.3 to 8.4, and when
> trying to use the parallel restore options I get the
> following error:
>
> > "pg_restore: [custom archiver] dumping a specific TOC
> data block out of order is not supported without ID on this
> input stream (fseek required)"
>
> This is the second or third report we've gotten of that,
> but nobody's
> been able to offer a reproducible test case.  Can
> you?
>

Hi Tom,

The schema is fairly large, but I will try.

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?

I guess what would help is some insight into what the error message means.

It appers to orginate in _PrintTocData in pg_backup_custom.c, but I don't really understand what's happening here at all, a wild guess is it's trying to seek to a particular toc entry in the file? or process the file sequentially?

http://doxygen.postgresql.org/pg__backup__custom_8c.html#6024b8108422e69062072df29f48506f

Glyn