Re: deferred writing of two-phase state files adds fragility - Mailing list pgsql-hackers

From Andres Freund
Subject Re: deferred writing of two-phase state files adds fragility
Date
Msg-id k7lk3vs2y3ju32mf2npmny3xl6izkoz7evihiceoyrysptmvbb@t6fjk6ls4cnb
Whole thread Raw
In response to Re: deferred writing of two-phase state files adds fragility  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

On 2024-12-05 11:21:12 -0500, Robert Haas wrote:
> On Wed, Dec 4, 2024 at 6:36 PM Andres Freund <andres@anarazel.de> wrote:
> > How did this corruption actually come about?  Did it actually really just
> > affect that single WAL segment? Somehow that doesn't seem too likely.
> 
> I don't know and might not be able to tell you even if I did.

Understandable. I was mainly asking because I don't really see it making sense
to make significant investments into coping with WAL getting arbitrarily
corrupted. But if there's some systematic issue leading to corruption, adding
more infrastructure to detect problems seems more worthwhile / realistic.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using Expanded Objects other than Arrays from plpgsql
Next
From: Peter Smith
Date:
Subject: Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY