Re: pg_upgrade instructions involving "rsync --size-only" might lead to standby corruption?

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: pg_upgrade instructions involving "rsync --size-only" might lead to standby corruption?
Date: 2023-07-01 09:02:23
Message-ID: 206B487C-B20E-4140-9C25-C6694CE7D4D4@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fast upgrade of highly available cluster is a vital part of being industry-acceptable solution for any data management system. Because the cluster is required to be highly available.

Without this documented technique upgrade of 1Tb cluster would last many hours, not seconds.
There are industry concerns about scalability beyond tens of terabytes per cluster, but such downtime would significantly lower that boundary.

> On 1 Jul 2023, at 01:16, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> If somebody
> wants to write a reliable tool for this to ship as part of PostgreSQL,
> well and good.

IMV that's a good idea. We could teach pg_upgrade or some new tool to do that reliably. The tricky part is that the tool must stop-start standby remotely...

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2023-07-01 09:04:05 Re: Do we want a hashset type?
Previous Message Julien Rouhaud 2023-07-01 07:49:36 Outdated description of PG_CACHE_LINE_SIZE