Re: Setting default version in Poudriere

On Saturday, July 6th, 2024 at 01:47, Shane Ambler <FreeBSD@ShaneWare.Biz> wrote:

> 
> 
> On 5/7/24 06:27, Pat wrote:
> 
> > Hello,
> > 
> > Got a couple of rather silly question, but I can't find a definitive answer to either.
> > 
> > If I build PostgreSQL15-server, I get version 15.7. That is the latest version, so not unexpected.
> > 
> > I would like to build version 15.6. Ideally I would like to have both versions available because for the most part I want to install 15.7, but I need 15.6 at the moment.
> > 
> > So my questions are:
> > How do I configure things to have both versions available?
> > If that is not possible, how do I set the default to be 15.6 for now, with the intent of undoing that after my testing?
> 
> 
> As far as ports go, you can configure the major postgresql version
> (14.x, 15.x), in make.conf add DEFAULT_VERSIONS= pgsql=15

Thank you Shane. I did actually figure that out over the weekend too.
First I tried setting that to 15.6 but got an error with a helpful
message that stated the acceptable versions were 12 - 16.

> 
> Considering you have a database requiring 15.6, you would have that
> installed and running already, I would suggest setting up 15.7 DB in a
> jail or second machine for regression tests and not need a second 15.6
> server running. So you would only need to build the newer version.
> 
> Are you aware of the postgresql versioning changes since 10? The first
> number is a major version, the second is a minor bug/security update
> 
> 15.6 to 15.7 is a minor update that can be done in-place.
> 
> From https://www.postgresql.org/support/versioning/
> 
> Minor release upgrades do not require a dump and restore; you simply
> stop the database server, install the updated binaries, and restart the
> server. Such upgrades might require additional steps so always read the
> release notes first.
> 
> Minor releases only contain fixes for frequently-encountered bugs,
> low-risk fixes, security issues, and data corruption problems. The
> community considers performing minor upgrades to be less risky than
> continuing to run an old minor version.

Yes, I am aware of all of that, but you had no way of knowing that, so
I appreciate the time you took to explain this.

I've been a PG DBA for 15 years :)

We have a good bit of custom code and the developer claims to have run
into an issue previously with a minor version change. So we want to
stand up a separate test environment for grins. And, I wouldn't mind
knowing how to do this for future reference, not just for PG but in
general.

Regards,
Pat

> 
> 
> --
> FreeBSD - the place to B...Serving Data
> 
> Shane Ambler