Re: BUG #16172: failure of vacuum file truncation can cause permanent data corruption

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: harukat(at)sraoss(dot)co(dot)jp
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16172: failure of vacuum file truncation can cause permanent data corruption
Date: 2019-12-20 05:22:22
Message-ID: 20191220.142222.460168291996674395.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

At Fri, 20 Dec 2019 11:00:28 +0900, TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message TAKATSUKA Haruka 2019-12-20 06:02:35 Re: BUG #16172: failure of vacuum file truncation can cause permanent data corruption
Previous Message Kyotaro Horiguchi 2019-12-20 04:55:42 Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)