Feedback-ID: i76984098:Fastmail
Message-ID: <b0f98040-e109-42ae-acf4-0f99babcecb1@aklaver.com>
Date: Fri, 5 Jun 2026 13:30:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Postgres 12 update to new major version
To: =?UTF-8?B?Qm9yaXMgRG92xI3DrWs=?= <bdovcik@gmail.com>,
 pgsql-general@lists.postgresql.org
References: 
 <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: 
 <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/b0f98040-e109-42ae-acf4-0f99babcecb1%40aklaver.com>
Precedence: bulk

On 6/5/26 5:11 AM, Boris Dovčík wrote:
> Hello all,
> 
> I have a question regarding the update of the production database 
> (multiple TB of data) from version 12 to higher major version. We would 

How many TB?

> like to jump to 15 or 16. DB is installed on a Linux server with one 
> replica on another, it is not on cloud.

What replication is being done now?

Where are the servers relative to each other network distance wise?

> 
> First question is should we perform updates one by one? 12 -> 13 -> 14 
> etc. or is it viable to jump to 16 right away? (We have few functions 
> but usually its plain tables)
> 
> Second we are contemplating options for the update since we are limited 
> with downtime. We could get 4 hours of downtime for the whole update 
> (either via pg_update or dumps). We are not sure how to estimate the 

Did you mean pg_upgrade?

> time for direct update or dumps. What would be the recommended way for it?
> 
> One option we see could be logical replication to the new major version 
> on a new machine, but we received feedback that in our setup it might 

What was the feedback that indicated it was not advisable?

> not be recommendable. Does it make sense to try logical replica? What 
> would be the downsides of it?
> 
> Best regards,
> Boris Dovčík


-- 
Adrian Klaver
adrian.klaver@aklaver.com