Rework SLRU I/O errors handle - Mailing list pgsql-hackers

From Maxim Orlov
Subject Rework SLRU I/O errors handle
Date
Msg-id CACG=ezZZfurhYV+66ceubxQAyWqv9vaUi0yoO4-t48OE5xc0DQ@mail.gmail.com
Whole thread
Responses Re: Rework SLRU I/O errors handle
List pgsql-hackers
Hi!

Beginning of the discussion is here [0].

Historically, the SLRU module was designed to handle 32-bit
transactions. However, it is now utilised for handling a variety of
object types, like TransactionId, MultixactId, MultiXactOffset,
QueuePosition, and so on. But the IO error reporting system is still
designed to support 32-bit XIDs exclusively.

The proposed patchset allows us to define a "custom" callback to
improve error messages.

The first two commits add a callback and test case. The subsequent ones
improve I/O error messages. The last one adds the XID epoch to the error
message. It's purely optional, but I think it would be useful.


--
Best regards,
Maxim Orlov.
Attachment

pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: typo in alter_table.sgml (was: Re: pgsql: Allow ALTER COLUMN SET EXPRESSION on virtual columns with CHECK)
Next
From: KAZAR Ayoub
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD