Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible
Date
Msg-id 32194.1551847358@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
List pgsql-bugs
Tree view 
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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15668: Server crash in transformPartitionRangeBounds