Thanks Kevin & Bruce for your replies,
 
It looks like this script deletes all of the data file directories (and the data files) from the postgres 8.4.3 instance.  Since we used the "-k" option, which calls for hard links rather than copying files to the new cluster, wouldn't this be deleting the files?  If so, the DB would be corrupted beyond recovery if we run it.  Or am I missing something?
 
thanks
 
Freddie
 
-------- Original Message --------
Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6
system files causing the file system to run out of space.
From: Kevin Grittner <kgrittn@ymail.com>
Date: Thu, March 07, 2013 8:14 am
To: "fburgess@radiantblue.com" <fburgess@radiantblue.com>,
"pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>

"fburgess@radiantblue.com" <fburgess@radiantblue.com> wrote:

> Does anyone know, what the names/location of the pg_upgrade
> cleanup scripts? We upgraded from 8.4.3 to 9.1.6

Sorry I didn't answer this sooner, but I didn't know off-hand and
hoped that someone who did would jump in.  Since that didn't happen
...

The file is delete_old_cluster.sh on most platforms.  The suffix is
.bat on Windows.

It can be run anytime after the upgrade *as long as you have not
moved the new cluster to the old location*.

Thanks to Bruce Momjian for telling me in chat when I asked just now.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs