To Clarify a bit about the Concerns here

We are actively participating in the PostgreSQL porting effort same as with the golang and Java one. So I would be very surprised if compiling fails :)


What is our concern is that when we compile Postgresql14 as default client lib for other consumers, those may not be backwards compatible with older Servers/libraries.

So if somebody needs to install postgresql 10 but we compile against 14 they are in trouble.

I think Yes we should go to 14 this time and we should ensure that older PostgreSQL cannot override the default (14) or that we remove them from system and ask users to compile those versions that they need for long term support themselves. We are Rolling release afterall and even Archlinux only has 13. So when we do this now only providing 14 in the system pre packaged is the best option for our resources.

Continued participation in the CI and porting efforts of Postgres will ensure it will be able to compile it with enough certainty that people will be able to do it easily.

This should ensure that we only need to do less migration work per release we switch and that we need to switch fewer releases. Also I saw Citus Extension coming in with 14 which I would love to start to use :)

Greetings
Till

On 26.02.22 08:16, Andreas Wacknitz wrote:
Hi all,

at the moment PostgreSQL 9.6 is our version that is being used for all
packages that need PostgreSQL. This version is not supported upstream
for some months now. The oldest supported version is 10 and this would
be the obvious new version to use for us.
Alas, obsoleting a PostgreSQL version in OpenIndiana means some work to
be done and it looks like nobody is interested enough to do this work
regularly.

So, my question is how we should proceed with PostgreSQL. Obsoleting 9.6
and using 10 as our default would mean that in less than 9 months
according to https://www.postgresql.org/support/versioning/ we will need
to touch PostgreSQL again. We will need a volunteer to do this or we
might think about skipping some versions of PostgreSQL now.

What is your opinion?

Andreas


_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev

_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev

Reply via email to