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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: 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 02:56:26
Message-ID: 20190306025626.GF30982@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 05, 2019 at 06:38:02AM +0000, PG Bug reporting form wrote:
> I guess that "Permission denied" is caused by antivirus software.
> However, this error caused data inconsistency in the table.

Most likely so. Please be very careful to disable that where Postgres
is running or apply filters. 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.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2019-03-06 03:04:59 Re: BUG #15667: "could not truncate file" error caused deleted rows to become visible
Previous Message Tom Lane 2019-03-05 22:59:59 Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)