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

2020-11-05 Thread Tom Lane
Michael Paquier writes: > (I got to wonder whether it would be worth the complexity to show more > information when using _dosmaperr() for WIN32 on stuff like > elog(ERROR, "%m"), just a wild thought). Maybe. It's been in the back of my mind for a long time that the _dosmaperr() mapping may be

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

2020-11-05 Thread Michael Paquier
On Wed, Nov 04, 2020 at 10:23:04PM -0500, Tom Lane wrote: > The latter case would result in a LOG message "unrecognized win32 error > code", so it would be good to know if any of those are showing up in > the postmaster log. Yeah. Not sure which one it could be here: https://docs.microsoft.com/en

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

2020-11-05 Thread Michael Paquier
On Thu, Nov 05, 2020 at 10:21:40AM +0100, Magnus Hagander wrote: > The problem with AVs generally doesn't come from them opening files in > non-share mode (I've, surprisingly enough, seen backup software that > causes that problem for example). It might happen on scheduled scans > for example, but

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

2020-11-05 Thread Magnus Hagander
On Thu, Nov 5, 2020 at 3:12 AM Michael Paquier wrote: > > 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, Postgre

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

2020-11-04 Thread Tom Lane
Michael Paquier writes: > On Wed, Nov 04, 2020 at 01:24:46PM +0100, Andreas Kretschmer wrote: >> 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 *

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

2020-11-04 Thread Michael Paquier
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 t

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

2020-11-04 Thread Andreas Kretschmer
> >PANIC: could not write to log file {} at offset {}, length {}: Invalid >argument > >(so I assumed it is related). > >attached is our configuration. > >Any ideas about what is the problem? or anything else I need to check? wild guess: Antivirus Software? > >

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

2020-11-04 Thread Adrian Klaver
On 11/4/20 2:24 AM, Shani Israeli wrote: Hi all, We are running PostgreSQL v9.5.19 over Windows Server 2012 R2, 16GB RAM. Lately, postgres started to crash (happened already 3 times ~once a month) and before its crashes I found this message in Event Log: PANIC:  could not write to log

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

2020-11-04 Thread David Day
wrote: > Hi all, > > We are running PostgreSQL v9.5.19 over Windows Server 2012 R2, 16GB RAM. > Lately, postgres started to crash (happened already 3 times ~once a month) > and before its crashes I found this message in Event Log: > > PANIC: could not write to log file {}

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

2020-11-04 Thread Shani Israeli
Hi all, We are running PostgreSQL v9.5.19 over Windows Server 2012 R2, 16GB RAM. Lately, postgres started to crash (happened already 3 times ~once a month) and before its crashes I found this message in Event Log: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument