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

From: Akira Kurosawa <a-kurosawa(at)bk(dot)jp(dot)nec(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, "Michael Paquier" <michael(at)paquier(dot)xyz>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible
Date: 2019-03-07 15:17:28
Message-ID: 4A60C8BEF6C7A64DA13F7CABB1D6016C2AF338@BPXM09GP.gisp.nec.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thank you for reply.

> Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-03-07 15:52:33 Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Previous Message Sandeep Thakkar 2019-03-07 15:16:35 Re: Instalation Bug