On 4/17/26 7:08 AM, Adrian Klaver wrote:
> On 4/17/26 6:20 AM, Jaya Sandeep wrote:
>> Upgrading to 16 version, guidance on this .
>
> Ron's point is that you are currently at Postgres 14.6 and there are
> approximately 4 years of bug fixes to the current stable 14.22 version
> as seen here:
>
> https://www.postgresql.org/docs/14/release.html
>
> It would be good idea to bring the 14 instance to as an up to date state
> as possible before moving on to latest major version(18), which in
> itself is a jump of 4 major versions.
Forgot to add to previous post. As you are changing the major version
you should go the Release Notes section for each major version(15-18)
and read through the notes for the changes that may affect you. It is
generally sufficient to look at just the initial release for each major
version as that where the new/breaking features are called out. Ideally
you would set up a test instance and verify that your code works in the
Postgres major version you wish to migrate to.
>
> As to the major to major upgrade I would suggest reading:
>
> https://clusterlabs.org/projects/pacemaker/doc/3.0/
> Pacemaker_Administration/html/
>
> and
>
> https://www.postgresql.org/docs/18/pgupgrade.html
>
>
>
>>
>> Thank you.
>>
>> Regards,
>> Neelam Jaya Sandeep
>> 9492727845
>>
>> On Fri, 17 Apr, 2026, 18:43 Ron Johnson, <ronljohnsonjr@gmail.com
>> <mailto:ronljohnsonjr@gmail.com>> wrote:
>>
>> On Fri, Apr 17, 2026 at 1:55 AM Jaya Sandeep
>> <jayasandy0909@gmail.com <mailto:jayasandy0909@gmail.com>> wrote:
>> [snip]
>>
>> *Details :*
>> Current version of PostgreSQL is *14.6 *
>>
>>
>> Step #1 is to update to fix the 3.5 years of bugs from 14.6 to
>> 14.22. Each node update should take no more than 5 minutes.
>>
>> -- Death to <Redacted>, and butter sauce.
>> Don't boil me, I'm still alive.
>> <Redacted> lobster!
>>
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
