| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Ryan Taylor <rgtaylor1989(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, markus(at)debian(dot)org, pgsql-pkg-debian(at)postgresql(dot)org |
| Subject: | Re: Missing Postgis.control |
| Date: | 2017-06-18 15:58:08 |
| Message-ID: | cd422b23-b8a3-bb5c-bdc4-83cbeb0e1ac7@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian |
On 06/18/2017 12:24 AM, Peter Eisentraut wrote:
> On 6/15/17 14:40, Markus Wanner wrote:
>> On 06/15/2017 05:43 PM, Ryan Taylor wrote:
>>> I thought the "postgis scripts" package was for updating the server's
>>> postgis version?
>> Correct, it's not strictly needed after CREATE EXTENSION, but the
>> extension keeps working without it.
>
> Hmm, this is true but might be confusing in the long run.
What would be less confusing?
I think it's similar enough to how Debian handles library upgrades.
>> While the *-scripts packages conflict against each other, the extension
>> packages (postgresql-X.Y-postgis-M.N) do not, allowing users to upgrade
>> without breaking existing installations.
>
> I don't understand this. Upgrade postgresql or upgrade postgis?
postgis
Use case: you installed postgis-2.2, created the extension, set it up to
be used in a database, and later do an 'apt-get dist-upgrade', giving
you postgis-2.3. Your database will continue to work (with the
postgis-2.2 version).
Upgrading PostgreSQL is an entirely different story.
Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | apt.postgresql.org repository | 2017-06-22 14:58:57 | pgbackrest updated to version 1.19-1.pgdg+2 |
| Previous Message | Peter Eisentraut | 2017-06-17 22:24:08 | Re: Missing Postgis.control |