Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible
Дата
Msg-id 32194.1551847358@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible  (Andres Freund <andres@anarazel.de>)
Ответы Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Список pgsql-bugs
Дерево обсуждения 
Andres Freund <andres@anarazel.de> writes:
> I don't think this has anything to do with the problem. Isn't this the
> known problem around truncation that Tom has recently talked about fixing?
> [1] https://www.postgresql.org/message-id/2348.1544474335%40sss.pgh.pa.us

Yeah, it sure looks like that same old issue to me.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: BUG #15668: Server crash in transformPartitionRangeBounds