FW: v8.2.6->8.2.7 upgrade renamed /var/lib/pgsql

From: "Hyatt, Gordon" <Gordon(dot)Hyatt(at)joslin(dot)harvard(dot)edu>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: FW: v8.2.6->8.2.7 upgrade renamed /var/lib/pgsql
Date: 2008-05-21 15:03:02
Message-ID: 85AC2B55AEF4CC41A2145B60C7F880740264EF@JDCMAIL4.joslin.harvard.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Sorry for the HTML posting previously.

I've already renamed the directories and the database is up and running.

I was just wondering if anyone else had this issue and what the reason, if known, for the renaming. I completely understand this type of behavior when doing a major version upgrade, but not a minor version patch like this.

Thanks,

Gord

________________________________________
From: Hyatt, Gordon
Sent: Wednesday, May 21, 2008 9:28 AM
To: pgsql-admin(at)postgresql(dot)org
Subject: v8.2.6->8.2.7 upgrade renamed /var/lib/pgsql

To all,

I just applied the v8.2.7 upgrade (from v8.2.6) on and FC8 server via yum.  The upgrade went OK, but the /var/lib/pgsql directory (with the existing data) was renamed to /var/lib/pgsql.old and a new (and empty) /var/lib/pgsql directory was created.

Does anyone know why this would have happened? 

The particular machine is an FC8, dual core AMD DELL with 4GB RAM running the x86_64 pg binaries.

I applied the same update (v8.2.6->8.2.7) to an FC7 Pentium4 box running the 32-bit pg binaries and did not have to rename the /var/lib/pgsql directories.

Has anyone else run into this?

Thanks, in advance,

Gord

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2008-05-21 19:07:07 Re: Trouble with recovering disc space
Previous Message Hyatt, Gordon 2008-05-21 13:27:51 v8.2.6->8.2.7 upgrade renamed /var/lib/pgsql