DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=qaAG3kGai1CDfgb1AkEALojAaMQCdYJqnqlr2R+Kz0r5OABprpRp4lFl6EQ0GV0l4O
	2d0MWnNe5MB49Ctum5Z6c46hg6YGaxyspv/kuB/TIiemc1BN7OAYladPvaow+XesmgvO
	TCUcYDNDFEf8b7ymvGelpeAvwb3whdJRfo8a4=
MIME-Version: 1.0
In-Reply-To: <4BC9F464.20901@pinpointresearch.com>
References: <g2z649cb4eb1004170931o39755d41k66e5be957fc89591@mail.gmail.com>
	<4BC9F464.20901@pinpointresearch.com>
Date: Sat, 17 Apr 2010 16:08:34 -0400
Message-ID: <v2m649cb4eb1004171308ve81536f2qf125a7722447c4ed@mail.gmail.com>
Subject: Re: pg_restore error
From: Bryan White <nicktook@gmail.com>
To: pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

> It was unclear from your email how you are creating the dump. Did you create
> the dump with the 8.1 or the 8.4 version of pg_dump? When upgrading, the
> docs recommend using the newer version of the dump utility: "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. Current releases of the dump programs can read
> data from any server version back to 7.0."

I messed up. I sent the stderr output of the dump to a text file and
never looked at it.  There was some sort of deadlock condition on a
particular table.  Another process tries to drop and recreate a table
during the time of the dump.

I was using the pg_dump from 8.1.  I have now dumped the database with
the 8.4 version.  It will be a couple hours before I have any results.

> How many cores are available on the new server?

The new server is a dual socket Nahalem.  8 cores, 16 threads, 48 GB
ram, 2 WAL drives in RAID1 and 12 database drives in RAID10.

-- 
Bryan White