| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Jeff Frost <jeff(at)pgexperts(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | "pgsql-pkg-yum(at)postgresql(dot)org" <pgsql-pkg-yum(at)postgresql(dot)org>, Jeff Frost <jfrost(at)pgexperts(dot)com> |
| Subject: | Re: PostGIS packages should not remove older libs |
| Date: | 2014-09-22 17:05:22 |
| Message-ID: | 542056D2.9090704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
On 09/21/2014 12:49 PM, Jeff Frost wrote:
>
>
>> On Sep 21, 2014, at 12:40, Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
>>
>> Can you please clarify this for me? Do you mean that we should keep .so
>> files of 2.1.3 , when someone upgrades to 2.1.4?
>
> I think he means when going from 2.0 to 2.1.
Correct. The postgis-#.#.so libraries are designed to be present
side-by-side so that users can do an online upgrade. But if
postgis-2.0.so gets deleted as soon as 2.1 is installed, then an online
upgrade isn't possible.
It also messes with replication to have the 2.0 library deleted, should
you upgrade the replica before the master, as is common.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lei Du | 2014-09-23 01:22:21 | 404 error for the RHEL 7 PostgreSQL 9.3 RPM |
| Previous Message | Jeff Frost | 2014-09-21 19:49:27 | Re: PostGIS packages should not remove older libs |