Re: Sketch of a fix for that truncation data corruption issue - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Sketch of a fix for that truncation data corruption issue
Date
Msg-id 20181211061551.4wbxeoafqjmjbirq@alap3.anarazel.de
Whole thread Raw
In response to Re: Sketch of a fix for that truncation data corruption issue  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
Hi,

On 2018-12-11 07:09:34 +0100, Laurenz Albe wrote:
> Tom Lane wrote:
> > We got another report today [1] that seems to be due to the problem
> > we've seen before with failed vacuum truncations leaving corrupt state
> > on-disk [2].  Reflecting on that some more, [...]
> 
> This may seem heretical, but I'll say it anyway.
> 
> Why don't we do away with vacuum truncation for good?
> Is that a feature that does anybody any good?
> To me it has always seemed to be more a wart than a feature, like
> someone just thought it was low hanging fruit without considering
> all the implications.

There's a lot of workloads that I've seen that'd regress. And probably a
lot more that we don't know about.  I don't see how we could go there.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Sketch of a fix for that truncation data corruption issue
Next
From: Ibrar Ahmed
Date:
Subject: Re: Interesting paper: Contention-Aware Lock Scheduling