On Fri, Apr 23, 2021 at 03:58:32PM +0000, Eric Hill wrote: > Hey, > > We are experiencing a periodic PostgreSQL crash. It happens overnight when automated processes are updating content on our website. My PostgreSQL version information is: > > PostgreSQL 11.10, compiled by Visual C++ build 1914, 64-bit > > It is running on Windows Server 2019 Standard. We were having this same crash on PostgreSQL 9.6, also running on Windows Server, I believe 2012, before a recent upgrade. Here is the relevant part of the log: > > 2021-04-23 03:20:57 EDT [5324]: LOG: connection received: host=10.120.80.162 port=54017 > 2021-04-23 03:20:57 EDT [5324]: LOG: connection authorized: user=dba_webjmp database=webjmp > 2021-04-23 03:21:00 EDT [15776]: LOG: server process (PID 14820) exited with exit code 1 > 2021-04-23 03:21:00 EDT [15776]: DETAIL: Failed process was running: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE; > 2021-04-23 03:21:00 EDT [15776]: LOG: terminating any other active server processes > 2021-04-23 03:21:00 EDT [5324]: WARNING: terminating connection because of crash of another server process > 2021-04-23 03:21:00 EDT [5324]: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. > 2021-04-23 03:21:00 EDT [5324]: HINT: In a moment you should be able to reconnect to the database and repeat your command. > > I would really like for PostgreSQL to produce a crashdump of this crash but one is not produced. I made a crashdumps folder in the data directory and gave it every permission I could think of, but no joy there. The mentioned query works just fine for me, so I doubt we could help without a core dump. Did you check the instructions at https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows#Using_crash_dumps_to_debug_random_and_unpredictable_backend_crashes?
