Re: POC: make mxidoff 64 bits

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Subject: Re: POC: make mxidoff 64 bits
Date: 2025-12-04 10:03:23
Message-ID: CACG=ezZHPFN2qdPAACDOpYmExUP_tujO2QbirqUB7jRWp+ADmA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 3 Dec 2025 at 15:04, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:

>
> There are plenty of such critical bytes in the system where a single bit
> flip renders the whole block unreadable. Actually, if we had checksums
> on SLRU pages, a single bit flip anywhere in the page would make the
> checksum fail and render the block unreadable.
>
> Correct. However, my concern about the lack of checksums for SLRU wasn't
about data loss and the impossibility of recovering it, but about the
impossibility of detecting the error. But it is how it is for now.

--
Best regards,
Maxim Orlov.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-12-04 10:04:37 Re: Use func(void) for functions with no parameters
Previous Message Maxim Orlov 2025-12-04 09:52:25 Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION