Re: checksum verification code breaks backups in v16-

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: checksum verification code breaks backups in v16-
Date: 2024-12-04 17:06:54
Message-ID: 2366343.1733332014@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Dec 4, 2024 at 11:10 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>> D'oh, sorry. Even so, I think I'd still vote for back-patching the v17
>> commit that inadvertently fixed this.

> Gotcha. Let's see if anyone else votes.

+1 for a back-patch of 025584a16. It's made it through a couple of
minor releases now, so I think it's more trustworthy than a
one-liner that you have low confidence in.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Hill 2024-12-04 17:07:32 CVE-2024-10979 - Does this affect Postgres built without --with-perl option?
Previous Message Robert Haas 2024-12-04 17:04:47 deferred writing of two-phase state files adds fragility