Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption
Date
Msg-id 20191220.142222.460168291996674395.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption  (TAKATSUKA Haruka <harukat@sraoss.co.jp>)
Responses Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption  (TAKATSUKA Haruka <harukat@sraoss.co.jp>)
List pgsql-bugs
Hello,

At Fri, 20 Dec 2019 11:00:28 +0900, TAKATSUKA Haruka <harukat@sraoss.co.jp> wrote in 
> 
> I found moving DropRelFileNodeBuffers() from top to end in function
> smgrtruncate() is a proper modification. It passed the regression test
> and this reproduction test.

I don't recall clealy but I think there was a thread similar to this
issue.  Assume that checkpoint was running concurrently, the
checkpoint can revive the just truncated blocks inadvertently with
bogus content.

reagards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)
Next
From: TAKATSUKA Haruka
Date:
Subject: Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption