| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Akira Kurosawa <a-kurosawa(at)bk(dot)jp(dot)nec(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, "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-08 01:39:40 |
| Message-ID: | 20190308013940.GF4099@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Mar 07, 2019 at 03:17:28PM +0000, Akira Kurosawa wrote:
>> 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.
>
> I understand.
> I hope that this problem will be fixed.
Of course. Thanks for the reminder, Tom and Andres.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wu, Fei | 2019-03-08 02:18:32 | A potential memory access violation in ecpg when using EXEC SQL INCLUDE |
| Previous Message | Julien Rouhaud | 2019-03-07 20:58:03 | Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000) |