Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: "'Kevin Grittner'" <Kevin.Grittner@wicourts.gov>,
	<pgsql-admin@postgresql.org>
Cc: <raghuchennuru@gmail.com>
References: <201104011542.p31Fg6L3025075@rs73.luxsci.com>
	<006201cbf2d1$1ea55730$5bf00590$@com>
	<4D99A788020000250003C21A@gw.wicourts.gov>
In-Reply-To: <4D99A788020000250003C21A@gw.wicourts.gov>
Subject: Re: DB Import Error...
Date: Tue, 5 Apr 2011 12:17:22 +0530
Organization: Zoniac Software Private Limited
Message-ID: <002501cbf35d$54246310$fc6d2930$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: Acvy4xmHbz+uTFhaQie5Vh8Fq0DAIQAbjFkA
Content-Language: en-us

> If you're upgrading to 9.0, I would start by following the
> recommended upgrade procedure and seeing whether these problems then
> exist in the new database.  Fixing old issues like this is one big
> reason for using the newer version of pg_dump.

How do I use the newer version of pg_dump (9.0.3 in this case) to take SQL
dump, when v8.2.3 is already installed in my server?  BTW, originally we've
installed v8.2.3 from the source (./configure, gmake, gmake install).  Even
if I try to install the new version 9.0.3 from source, will that not
overwrite existing directories, files, binaries, etc.?

Our current v8.2.3 setup:
Installation directory: /usr/local/pgsql
Port: 5432

Any procedure/steps/advice/suggestion to take dump using latest version of
pg_dump without disturbing old database cluster is appreciated.

NOTE: It's not one single database server, we've multiple onsite customer
servers that has to be upgraded, hence I would like to address this issue in
general.