Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible - Mailing list pgsql-bugs

From Akira Kurosawa
Subject Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Date
Msg-id 4A60C8BEF6C7A64DA13F7CABB1D6016C2AF338@BPXM09GP.gisp.nec.co.jp
Whole thread Raw
In response to Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Thank you for reply.

> 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.


Regards,
Akira Kurosawa




pgsql-bugs by date:

Previous
From: Sandeep Thakkar
Date:
Subject: Re: Instalation Bug
Next
From: Tom Lane
Date:
Subject: Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)