| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Boris Dovčík <bdovcik(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres 12 update to new major version |
| Date: | 2026-06-05 20:30:55 |
| Message-ID: | b0f98040-e109-42ae-acf4-0f99babcecb1@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-06-05 21:59:20 | Re: Postgres 12 update to new major version |
| Previous Message | Bruce Momjian | 2026-06-05 20:08:31 | Re: Postgres 12 update to new major version |