On Thu, Apr 3, 2025 at 3:25 AM Peter Eisentraut wrote:
>
> On 11.03.25 11:42, Peter Eisentraut wrote:
> > Here is an updated patch that works more along those lines. It adds a
> > pg_upgrade option --update-checksums, which activates the code to
> > rewrite the checksums. You must specify this o
On 11.03.25 11:42, Peter Eisentraut wrote:
Here is an updated patch that works more along those lines. It adds a
pg_upgrade option --update-checksums, which activates the code to
rewrite the checksums. You must specify this option if the source and
target clusters have different checksum sett
On 21.02.25 00:41, Robert Treat wrote:
On Tue, Aug 27, 2024 at 5:57 PM Nathan Bossart wrote:
On Mon, Aug 26, 2024 at 08:23:44AM +0200, Peter Eisentraut wrote:
The purpose of this patch is to allow using pg_upgrade between clusters that
have different checksum settings. When upgrading between
On Tue, Aug 27, 2024 at 5:57 PM Nathan Bossart wrote:
>
> On Mon, Aug 26, 2024 at 08:23:44AM +0200, Peter Eisentraut wrote:
> > The purpose of this patch is to allow using pg_upgrade between clusters that
> > have different checksum settings. When upgrading between instances with
> > different ch
On Mon, Aug 26, 2024 at 08:23:44AM +0200, Peter Eisentraut wrote:
> The purpose of this patch is to allow using pg_upgrade between clusters that
> have different checksum settings. When upgrading between instances with
> different checksum settings, the --copy (default) mode automatically sets
> (
Hi Peter,
I've applied and tested your patch, it works at least on MacOS with
meson build. A couple of thoughts about this patch inline below.
On Mon, Aug 26, 2024 at 8:23 AM Peter Eisentraut wrote:
> The purpose of this patch is to allow using pg_upgrade between clusters
> that have different c
