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

From Michael Paquier
Subject Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Date
Msg-id 20190306025626.GF30982@paquier.xyz
Whole thread Raw
In response to BUG #15667: "could not truncate file" error caused deleted rows to become visible  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible  (Andres Freund <andres@anarazel.de>)
List 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

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Next
From: Andres Freund
Date:
Subject: Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible