From: Bryan White <nicktook@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: pg_restore error
Date: Sat, 17 Apr 2010 16:08:34 -0400
Message-ID: <v2m649cb4eb1004171308ve81536f2qf125a7722447c4ed@mail.gmail.com> (raw)
In-Reply-To: <4BC9F464.20901@pinpointresearch.com>
References: <g2z649cb4eb1004170931o39755d41k66e5be957fc89591@mail.gmail.com>
<4BC9F464.20901@pinpointresearch.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: nicktook@gmail.com
Subject: Re: pg_restore error
In-Reply-To: <v2m649cb4eb1004171308ve81536f2qf125a7722447c4ed@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox