| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, aki-kurosawa(at)vt(dot)jp(dot)nec(dot)com, 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-06 04:42:38 |
| Message-ID: | 32194.1551847358@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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] /message-id/2348.1544474335%40sss.pgh.pa.us
Yeah, it sure looks like that same old issue to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-03-06 06:48:25 | Re: BUG #15668: Server crash in transformPartitionRangeBounds |
| Previous Message | Andres Freund | 2019-03-06 03:04:59 | Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible |