Thread: Re: Upgrading 9.1.17 to which version?

Hi,

 

I've just inherited an ancient install of 9.1.17 after our tech guy left, on what turns out to be a rapidly dying server and being a total newb to PostgreSQL (and not much more advanced on Linux) I'm a little stuck on the way ahead.

 

I've managed to secure a decent new server for a new install of PostgreSQL which runs CentOS 7.6 (Minimal). CentOS 7.6's standard PostgreSQL package seems to be 9.2.24 which is obviously no longer supported so probably doesn't get us much further ahead in the short term. As part of this upgrade we'd also like to implement support for pg_trgm which apparently needs >=9.6.

 

I spent most of yesterday trying to get 9.6.13 installed from the PostgreSQL Yum repository and finally got it working with the initdb stuff stored on a non-default dedicated partition (RAID10 array) only to find that psql didn't work and was complaining about a missing libpq.so.5. Not sure if that's a common problem?

 

My (admittedly loose) logic tells me that upgrading from 9.1.x to 9.6.x is probably a safer option than making the leap up to 10.x or 11.x

but I wonder whether that might be an easier/more reliable option from an install and point of view and certainly preferable in the long term. Any advice on where to go?

On 16/05/2019 18:20, Ron wrote:
> On 5/16/19 4:36 AM, nigel.andersen@gmx.com wrote:
>> Hi,
>> I've just inherited an ancient install of 9.1.17 after our tech guy
>> left, on what turns out to be a rapidly dying server and being a total
>> newb to PostgreSQL (and not much more advanced on Linux) I'm a little
>> stuck on the way ahead.
>> I've managed to secure a decent new server for a new install of
>> PostgreSQL which runs CentOS 7.6 (Minimal). CentOS 7.6's standard
>> PostgreSQL package seems to be 9.2.24 which is obviously no longer
>> supported so probably doesn't get us much further ahead in the short
>> term. As part of this upgrade we'd also like to implement support for
>> pg_trgm which apparently needs >=9.6.
>> I spent most of yesterday trying to get 9.6.13 installed from the
>> PostgreSQL Yum repository and finally got it working with the initdb
>> stuff stored on a non-default dedicated partition (RAID10 array) only
>> to find that psql didn't work and was complaining about a missing
>> libpq.so.5. Not sure if that's a common problem?
>
> What packages did you install?
>
>> My (admittedly loose) logic tells me that upgrading from 9.1.x to
>> 9.6.x is probably a safer option than making the leap up to 10.x or 11.x
>
> No, not really.
>
>> but I wonder whether that might be an easier/more reliable option from
>> an install and point of view and certainly preferable in the long
>> term. Any advice on where to go?
>
> 11.x would be best, since it's EOL is furthest in the future.
> 9.6 would be best, because it's had more bug-fix releases.
>

Aren't all important bugfixes backported to every non-EOL affected
majors at once?


Correct me if I'm wrong but I thought that's the reason minors are
released at unison for all majors.



> :)
>
> --
> Angular momentum makes the world go 'round.

--
Regards

Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology

--


Notice:  This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necessarily reflect the opinions and views of the members of the
Ocado Group. 

 

If you are not the intended recipient, please notify us
immediately and delete all copies of this message. Please note that it is
your responsibility to scan this message for viruses. 

 

Fetch and Sizzle
are trading names of Speciality Stores Limited and Fabled is a trading name
of Marie Claire Beauty Limited, both members of the Ocado Group.

 


References to the “Ocado Group” are to Ocado Group plc (registered in
England and Wales with number 7098618) and its subsidiary undertakings (as
that expression is defined in the Companies Act 2006) from time to time.  
The registered office of Ocado Group plc is Buildings One & Two, Trident
Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9UL.

On 5/16/19 10:38 AM, Fabio Ugo Venchiarutti wrote:
> 
> 

>>
>> 11.x would be best, since it's EOL is furthest in the future.
>> 9.6 would be best, because it's had more bug-fix releases.
>>
> 
> Aren't all important bugfixes backported to every non-EOL affected 
> majors at once?
> 
> 
> Correct me if I'm wrong but I thought that's the reason minors are 
> released at unison for all majors.

True. The possible issue is that the newest version has been out for the 
shortest period of time and contains new code that may not have been 
exercised enough yet to catch all as yet hidden bugs. Older versions 
have been run longer and under more scenarios so the expectation is more 
of the bugs have been flushed out.

> 
> 
> 
>> :)
>>
>> -- 
>> Angular momentum makes the world go 'round.
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com