On Mon, Mar 30, 2026 at 11:37 AM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> On Mon, Mar 30, 2026 at 4:16 AM Balaji Ram <balajiram.ganesan@gmail.com> wrote:
>>
>> Hi Everyone,
>>
>> I'm planning to upgrade a standalone PostgreSQL cluster from **13.20 to 17.9**. I haven’t performed a major version
upgradewith such a large version gap before, so I’d appreciate any guidance on best practices, recommended approaches,
andthings to watch out for.
>
>
> 1. Read the PG 14, 15, 16 and 17 release notes.
> 2. Being on the latest is the latest release (in this case, 13.23) is always Best Practice.
>
+1 to the above, pay special attention to any incompatibilities
information. If you want to be really thorough, you should look at the
first few minor release for each branch to see if there are any system
catalog updates or reindexing type activities you need to deal with.
Also, if you have any extensions, you'll need to verify that those
will also survive such a big version jump; there's an outside chance
you may need to stop at some major version along the way.
Oh. and if you don't have a strong reason against it, most would
probably recommend you go to v18 at this point.
Robert Treat
https://xzilla.net
