--0050450163d51ed5c604842c9f97
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm trying to use the -j option on pg_restore while restoring a database
into PG 8.4.3.

The dump was executed on PG 8.3.7 (Windows, Server 2003) using:

pg_dump -Fc -U postgres mydb > mydb.backup

This results in a ~3.4 GB dump file.

When I try to restore I'm using:

pg_restore -d mydb -U postgres -j 4 mydb.backup

This results in an error:

pg_restore: [custom archiver] dumping a specific TOC data block out of order
not supported without ID on this input stream (fseek required)

The dump works fine if I omit the -j option. What am I doing wrong?

Thanks,

Justin

--0050450163d51ed5c604842c9f97
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I'm trying to use the -j option on pg_restore while restorin=
g a database into PG 8.4.3.=A0 <br><br>The dump was executed on PG 8.3.7 (W=
indows, Server 2003) using:<br><br><div style=3D"margin-left: 40px;">pg_dum=
p -Fc -U postgres mydb > mydb.backup<br>
</div><br>This results in a ~3.4 GB dump file.<br><br>When I try to restore=
I'm using:<br><br><div style=3D"margin-left: 40px;">pg_restore -d mydb=
-U postgres -j 4 mydb.backup<br></div><br>This results in an error:<br><br=
>
<div style=3D"margin-left: 40px;">pg_restore: [custom archiver] dumping a s=
pecific TOC data block out of order not supported without ID on this input =
stream (fseek required)<br></div><br>The dump works fine if I omit the -j o=
ption.=A0 What am I doing wrong?<br>
<br>Thanks,<br><br>Justin<br>

--0050450163d51ed5c604842c9f97--

Justin Falk wrote:
> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
>
> pg_dump -Fc -U postgres mydb > mydb.backup
>
> This results in a ~3.4 GB dump file.
>
> When I try to restore I'm using:
>
> pg_restore -d mydb -U postgres -j 4 mydb.backup
>
> This results in an error:
>
> pg_restore: [custom archiver] dumping a specific TOC data block out of order
> not supported without ID on this input stream (fseek required)
>
> The dump works fine if I omit the -j option. What am I doing wrong?

Perhaps this is fixed in 8.3.10.

--
Bruce Momjian <bruce [at] momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Justin Falk <jfalkmu [at] gmail.com> writes:
> When I try to restore I'm using:
> pg_restore -d mydb -U postgres -j 4 mydb.backup
> This results in an error:
> pg_restore: [custom archiver] dumping a specific TOC data block out of order
> not supported without ID on this input stream (fseek required)

There was something similar reported here:
http://archives.postgresql.org/pgsql-admin/2010-04/msg00237. php
but we haven't got to the bottom of it yet. Can you create a
self-contained test case?

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

--001517476474c3888a0484ad1173
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Apr 14, 2010 at 2:38 AM, Justin Falk <jfalkmu [at] gmail.com> wrote:

> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
>
> pg_dump -Fc -U postgres mydb > mydb.backup
>
> This results in a ~3.4 GB dump file.
>
> When I try to restore I'm using:
>
> pg_restore -d mydb -U postgres -j 4 mydb.backup
>
> This results in an error:
>
> pg_restore: [custom archiver] dumping a specific TOC data block out of
> order not supported without ID on this input stream (fseek required)
>
> The dump works fine if I omit the -j option. What am I doing wrong?
>

I'm pretty sure that you need to use the 8.4 version of pg_dump when you
create the backup file, then it should work.

--Scott

>
> Thanks,
>
> Justin
>

--001517476474c3888a0484ad1173
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Wed, Apr 14, 2010 at 2:38 AM, Justin Falk=
<span dir=3D"ltr"><<a href=3D"mailto:jfalkmu [at] gmail.com">jfalkmu [at] gmail.c=
om</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br><br>I'm trying to use the -j option on pg_restore while restorin=
g a database into PG 8.4.3.=A0 <br><br>The dump was executed on PG 8.3.7 (W=
indows, Server 2003) using:<br><br><div style=3D"margin-left:40px">pg_dump =
-Fc -U postgres mydb > mydb.backup<br>

</div><br>This results in a ~3.4 GB dump file.<br><br>When I try to restore=
I'm using:<br><br><div style=3D"margin-left:40px">pg_restore -d mydb -=
U postgres -j 4 mydb.backup<br></div><br>This results in an error:<br><br>

<div style=3D"margin-left:40px">pg_restore: [custom archiver] dumping a spe=
cific TOC data block out of order not supported without ID on this input st=
ream (fseek required)<br></div><br>The dump works fine if I omit the -j opt=
ion.=A0 What am I doing wrong?<br>
</blockquote><div><br></div><div>I'm pretty sure that you need to use t=
he 8.4 version of pg_dump when =A0you create the backup file, then it shoul=
d work.</div><div><br></div><div>--Scott =A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex;">

<br>Thanks,<br><font color=3D"#888888"><br>Justin<br>
</font></blockquote></div><br>

--001517476474c3888a0484ad1173--

Justin Falk <jfalkmu [at] gmail.com> wrote:

> I'm trying to use the -j option on pg_restore while restoring a
> database into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:

Using the 8.4.3 version of pg_dump, as recommended in the
documentation?:

http://www.postgresql.org/docs/8.4/interactive/migration.htm l

"It is recommended that you use the pg_dump and pg_dumpall programs
from the newer version of PostgreSQL, to take advantage of any
enhancements that might have been made in these programs."

-Kevin

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

On Wed, Apr 14, 2010 at 12:38 AM, Justin Falk <jfalkmu [at] gmail.com> wrote:
> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:

I think you have to dump with 8.4 to use -j on restore.

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Scott Mead <scott.lists [at] enterprisedb.com> writes:
> On Wed, Apr 14, 2010 at 2:38 AM, Justin Falk <jfalkmu [at] gmail.com> wrote:
>> This results in an error:
>> pg_restore: [custom archiver] dumping a specific TOC data block out of
>> order not supported without ID on this input stream (fseek required)

> I'm pretty sure that you need to use the 8.4 version of pg_dump when you
> create the backup file, then it should work.

While that might be best practice, it's not clear why testing fails to
reproduce the problem, as we found in the other recent thread. In any
case it'd be nice to deliver a more helpful error message, if the
combination really doesn't work in some cases. But we need a
reproducible case to figure out why it's failing.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

On Tue, Apr 20, 2010 at 11:32 AM, Tom Lane <tgl [at] sss.pgh.pa.us> wrote:
> There was something similar reported here:
> http://archives.postgresql.org/pgsql-admin/2010-04/msg00237. php
> but we haven't got to the bottom of it yet.

That issue turned out to be me not paying attention to the pg_dump
output. There was a deadlock with another process trying to recreate
a table. This caused the dump file to be incomplete.


--
Bryan White

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin