Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
Cc: Shani Israeli <sisraeli(at)illusivenetworks(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument
Date: 2020-11-05 02:10:12
Message-ID: 20201105021012.GD1632@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 04, 2020 at 01:24:46PM +0100, Andreas Kretschmer wrote:
>> Any ideas about what is the problem? or anything else I need to check?
>
> wild guess: Antivirus Software?

Perhaps not. To bring more context in here, PostgreSQL opens any
files on WIN32 with shared writes and reads allowed to have an
equivalent of what we do on all *nix platforms. Note here that the
problem comes from a WAL segment write, which is done after the file
handle is opened in shared mode. As long as the fd is correctly
opened, any attempt for an antivirus software to open a file with an
exclusive write would be blocked, no?
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-11-05 03:23:04 Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument
Previous Message Nikolay Samokhvalov 2020-11-05 02:01:37 Re: Christopher Browne