DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=L3iKtsXFlummqXkQ3T06/ViUNOWcg5eopitd/QxunBBfrnno2ljkYW0XgcBVsvKfs7
	+jVhJbxDq22rs9HEBis/kCd3XkDL02wtbZ2SOU50pscrwcM3wfe7OV6hJNzL16FNH7em
	Zy0gHfgLsJ92hx5XuEaeH4a3/huQL9nytBcec=
MIME-Version: 1.0
Date: Sat, 17 Apr 2010 12:31:21 -0400
Message-ID: <g2z649cb4eb1004170931o39755d41k66e5be957fc89591@mail.gmail.com>
Subject: pg_restore error
From: Bryan White <nicktook@gmail.com>
To: pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

I am trying to load a data base using pg_restore.  We are migrating to
a new server and I want to see if I can make the load go faster if I
load with pg_restore instead of psql.

The old server is:
CentOS upgraded to 5.4 64bit with the stock PostgreSQL 8.1.
The dump file was created with:
     pg_dump --format=c --file=ec.restore ec
where ec is the name of the database.  It is encoded SQL_ASCII.  I
plan on converting to UTF-8 but I can't do that quite yet.

The new server is
CentOS 5.4 64 bit with PostgreSQL 8.4 installed from the YUM repo on
the PostgreSQL site.

The restore command is:
    createdb -E SQL_ASCII -T template0 ec
    pg_restore -dec -j2 ec.restore

I get this 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)
pg_restore: [archiver] worker process failed: exit code 1

It seems to run if I ommit the -j2 option. (Though as of this moment
is has not completed).  Is there a known problem with using parallel
loading in 8.4 from a file created with an 8.1 database?

--
Bryan White