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

Поиск
Список
Период
Сортировка
Искать
От
Kyotaro Horiguchi
Тема
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption
Дата
Msg-id
20191220.142222.460168291996674395.horikyota.ntt@gmail.com
Ответ на
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption (TAKATSUKA Haruka)
Список
Дерево обсуждения
BUG #16172: failure of vacuum file truncation can cause permanent data corruption PG Bug reporting form <noreply@postgresql.org>
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption TAKATSUKA Haruka <harukat@sraoss.co.jp>
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption TAKATSUKA Haruka <harukat@sraoss.co.jp>
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: BUG #16172: failure of vacuum file truncation can causepermanent data corruption TAKATSUKA Haruka <harukat@sraoss.co.jp> 
Hello,

At Fri, 20 Dec 2019 11:00:28 +0900, TAKATSUKA Haruka  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 по дате отправления
Предыдущее
От: Kyotaro Horiguchi
Дата:
Следующее
От: TAKATSUKA Haruka
Дата:
FAQ