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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Дата
Msg-id 20190306025626.GF30982@paquier.xyz
обсуждение исходный текст
Ответ на BUG #15667: "could not truncate file" error caused deleted rows to become visible  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible
Список 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

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Следующее
От: Andres Freund
Дата:
Сообщение: Re: BUG #15667: "could not truncate file" error caused deleted rowsto become visible