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

2020-11-04 Thread Andreas Kretschmer
On 4 November 2020 11:24:03 CET, 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

Race condition with restore_command on streaming replica

2020-11-04 Thread Brad Nicholson
Hi, I've recently been seeing a race condition with the restore_command on replicas using streaming replication. On the primary, we are archiving wal files to s3 compatible storage via pgBackRest. In the recovery.conf section of the postgresql.conf file on the replicas, we define the restore

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

2020-11-04 Thread David Day
I Could not read your config file but What is the size of the Postgres log file? Do you have a log rotation policy on it? Perhaps your Postgres log level is to high or your connections are generating a lot of errors that need investigating. Dave On Wed, Nov 4, 2020 at 5:24 AM Shani Israeli

Re: CentOS 7 yum package systemd bug?

2020-11-04 Thread Magnus Hagander
On Wed, Nov 4, 2020 at 9:45 AM Laurenz Albe wrote: > > On Tue, 2020-11-03 at 09:42 -0600, Doug Whitfield wrote: > > Unclear to me if this is a systemd bug or a Postgresql 12 bug, so I figured > > I would get some thoughts here before reporting in detail. > > > > It is pretty simple to reproduce.

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: Christopher Browne

2020-11-04 Thread Dave Cramer
On Wed., Nov. 4, 2020, 8:10 p.m. raf, wrote: > On Wed, Nov 04, 2020 at 06:29:18PM -0500, Steve Singer > wrote: > > > > > It is with much sadness that I am letting the community know that Chris > > Browne passed away recently. > > > > Chris had been a long time community member and was active on

Re: Christopher Browne

2020-11-04 Thread Nikolay Samokhvalov
What a sad news. Rest In Peace, Christopher. Condolences to friends and family. On Wed, Nov 4, 2020 at 15:29 Steve Singer wrote: > > It is with much sadness that I am letting the community know that Chris > Browne passed away recently. > > Chris had been a long time community member and was

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

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: Christopher Browne

2020-11-04 Thread Bikram Majumdar
So sorry to hear this news. On Wed, Nov 4, 2020, 17:29 Steve Singer wrote: > > It is with much sadness that I am letting the community know that Chris > Browne passed away recently. > > Chris had been a long time community member and was active on various > Postgresql mailing lists. He was a

Re: Christopher Browne

2020-11-04 Thread Christophe Pettus
> On Nov 4, 2020, at 15:29, Steve Singer wrote: > > It is with much sadness that I am letting the community know that Chris > Browne passed away recently. I'm so sorry to hear this. I did not know him well, but he was always a kind and friendly face anytime I saw him at events. -- --

Re: Christopher Browne

2020-11-04 Thread Jan Wieck
Christopher Browne was my colleague and friend at Afilias and past for more than a decade. I have countless memories that connect us. He will be missed. Jan On Wed, Nov 4, 2020, 18:29 Steve Singer wrote: > > It is with much sadness that I am letting the community know that Chris > Browne

Re: Christopher Browne

2020-11-04 Thread raf
On Wed, Nov 04, 2020 at 06:29:18PM -0500, Steve Singer wrote: > > It is with much sadness that I am letting the community know that Chris > Browne passed away recently. > > Chris had been a long time community member and was active on various > Postgresql mailing lists. He was a member of

Re: Christopher Browne

2020-11-04 Thread Joe Conway
On 11/4/20 7:45 PM, Jan Wieck wrote: > Christopher Browne was my colleague and friend at Afilias and past for more > than > a decade. I have countless memories that connect us. He will be missed. > > > Jan He will definitely be missed. Rest in Peace Chris. Joe > On Wed, Nov 4, 2020, 18:29

Christopher Browne

2020-11-04 Thread Steve Singer
It is with much sadness that I am letting the community know that Chris Browne passed away recently. Chris had been a long time community member and was active on various Postgresql mailing lists. He was a member of the funds committee, the PgCon program committee and served on the board

Re: Christopher Browne

2020-11-04 Thread Pavan Pusuluri
So sorry to hear the news. May his soul rest in peace. Regards Pavan On Wed, Nov 4, 2020, 6:46 PM Jan Wieck wrote: > Christopher Browne was my colleague and friend at Afilias and past for > more than a decade. I have countless memories that connect us. He will be > missed. > > > Jan > > On

Re: Christopher Browne

2020-11-04 Thread Vincenzo Campanella
RIP Chris Il 05.11.2020 02:09, raf ha scritto: On Wed, Nov 04, 2020 at 06:29:18PM -0500, Steve Singer wrote: It is with much sadness that I am letting the community know that Chris Browne passed away recently. Chris had been a long time community member and was active on various Postgresql

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

Re: CentOS 7 yum package systemd bug?

2020-11-04 Thread Laurenz Albe
On Tue, 2020-11-03 at 09:42 -0600, Doug Whitfield wrote: > Unclear to me if this is a systemd bug or a Postgresql 12 bug, so I figured I > would get some thoughts here before reporting in detail. > > It is pretty simple to reproduce. If you start your standby server with > incorrect username or