We get around this issue by creating a symbolic link called "current" that points to the version of Postgres that we want our servers to use by default:
ln -s /var/lib/pgsql/9.1 /var/lib/pgsql/current The symbolic link is changed whenever we do an upgrade so it doesn't interfere with anything that we may already have configured. Thanks, Bobby On 1/31/12 8:14 AM, "Marti Raudsepp" <ma...@juffo.org> wrote: >On Tue, Jan 31, 2012 at 00:41, Jerry Richards ><jerry.richa...@teotech.com> wrote: >> I just installed postgreSQL 9.1 and noticed it hard-codes the folder >> /var/lib/pgsql/9.1 and it hard-codes the service name to be >>postgresql91. > >> Why is the hard-coded version included in the naming? > >Note that this is done by Linux distributions, vanilla PostgreSQL >doesn't use version-specific paths. > >The reason is that the PostgreSQL on-disk format is not >forward-compatible. In order to upgrade from one Postgres version to >the next, you need to have *both* versions installed at once. As >annoying as it is, version-specific paths is a pretty foolproof way to >enable that. > >Regards, >Marti -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
