"fburg...@radiantblue.com" <fburg...@radiantblue.com> wrote:
> We did use pg_upgrade with the hard link option. We are not sure > if we ran the cleanup script. > Can we run this script now, even though its month's after we did > the upgrade? > Everything in the .../19177 directories represent data files > migrated over form postgres 8.4.3. All new files get placed into > the .../PG_9.1_201105231/16411 directories. > The vast majority of the "orphan" files are from the > /opt/PostgreSQL/9.1/data/user_data/19177 directory. I don't have any reason to expect that you *can't* run the script at this point; but being a cautious person, I would do this at a point where I was confident I could recover from a backup, and I would read through the scripts carefully before applying them. What you want to be really careful that you *don't* do is to modify or truncate any of the hard-linked files, as they are quite likely to still be just another name for the same file that is in use for production under the newer version. You want to simply remove the older directory entry pointing to the file. http://www.linfo.org/hard_link.html -- 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
