| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 03:04:59 |
| Message-ID: | 20190306030459.coyyy2uymbfipm4g@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2019-03-06 11:56:26 +0900, Michael Paquier wrote:
> Windows is not concurrent safe by default when it comes to handle
> writes, and Postgres uses a wrapper for open() which makes use of some
> concurrent-safe options when handling files to avoid such problems.
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
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-06 04:42:38 | Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible |
| Previous Message | Michael Paquier | 2019-03-06 02:56:26 | Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible |