[postgis-devel] A snap for PostGis

[Julia Palandri]

Hi,

On Tue, Nov 29, 2016 at 1:10 PM Darafei "Komяpa" Praliaskouski <
me at komzpa.net> wrote:

>
> At the moment there are different snaps for each major version available
> (snap find postgres shows this), all of these in the stable channel. We
> are, however, working towards having smarter channels. Right now there is
> edge, which you can update with every commit to trunk. There's also beta,
> candidate, and of course stable.
> We're aiming at having 9.6/stable, 9.6/candidate, 9.6/beta, 9.6/edge,
> 9.5/stable, 9.5/candidate, and so on, and also a "magic" latest family:
> latest/edge, latest/beta, etc. latest'stable would be the version you get
> when you ask the system to install any snap, without manually specifying
> the major version and flavour.
>
>
> This describes install, but not upgrade process.
>
>
Well, rather, I was trying to explain that with different "series" for each
major version, updates should be handled ok.


> If you upgrade by just replacing binaries, you should keep in mind
> postgres 9.6 can't work with database created in postgres 9.4 - so, you
> need pg_upgrade (+ several manual steps) to perform the upgrade.
>
>
Right. So, I've been talking with the people that has been helping with the
postgres snap, and they told that maybe the content interface might be able
to give a hand for plupgrades between major versions.


> If you install postgis, you have a postgis binary for each version of
> postgis for each version of postgres. After you connect to postgres
> database, you can switch the version of extension used, and several running
> simultaneous queries can be using different versions of postgis.
>
> Packaging postgis+postgres in single package has a disadvantage - you
> can't use more than two extensions at the same time in that scheme.
>
> How is it going to be handled?
>

Right, so maybe the solution would be to create a pg interface. Or again,
we could use the content interface to create a way for extensions to be
placed where PG can find them. This might need some coordinated work
with Command
Prompt to get the PG snap to look for extensions there. If you're
interested in investing some time into it, so are we :) We are writing to
upstreams also to know what they need (even though we can't promise it will
be ready soon), but knowing what's lacking to snaps for it to be adopted
certainly can modify our roadmap.

Again, if interested, we might be able to coordinate a meeting with other
people involved to try to find a way :)

Best,

Julia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20161202/b8feddfd/attachment.html>