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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Дата
Msg-id 20190308013940.GF4099@paquier.xyz
обсуждение исходный текст
Ответ на Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible  (Akira Kurosawa <a-kurosawa@bk.jp.nec.com>)
Список pgsql-bugs
Дерево обсуждения 
On Thu, Mar 07, 2019 at 03:17:28PM +0000, Akira Kurosawa wrote:
>> 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.
>
> I understand.
> I hope that this problem will be fixed.

Of course.  Thanks for the reminder, Tom and Andres.
--
Michael
Вложения

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

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Следующее
От: "Wu, Fei"
Дата:
Сообщение: A potential memory access violation in ecpg when using EXEC SQLINCLUDE