From: | Bobby Dewitt <Bdewitt(at)appriss(dot)com> |
---|---|
To: | Marti Raudsepp <marti(at)juffo(dot)org>, Jerry Richards <jerry(dot)richards(at)teotech(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why Hard-Coded Version 9.1 In Names? |
Date: | 2012-02-01 14:28:30 |
Message-ID: | CB4EB58C.3FEE2%bdewitt@appriss.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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" <marti(at)juffo(dot)org> wrote:
>On Tue, Jan 31, 2012 at 00:41, Jerry Richards
><jerry(dot)richards(at)teotech(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Marti Raudsepp | 2012-02-01 14:33:07 | Re: parameter "vacuum_defer_cleanup_age" |
Previous Message | Volodymyr Kostyrko | 2012-02-01 13:45:44 | Re: Help speeding up a left join aggregate |