From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: sujeet.chaurasia@lisec.com
Subject: BUG #17636: terminating connection because of crash of another server process
Date: Wed, 12 Oct 2022 11:22:26 +0000
Message-ID: <17636-e10e2465ca1f6a74@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17636
Logged by: Sujeet Swaminath
Email address: sujeet.chaurasia@lisec.com
PostgreSQL version: 12.11
Operating system: Windows
Description:
We are facing this issue with POSTGRES 12.11, only on windows OS, with Linux
OS, it works fine,
if the executable that is using the database session crashes, then the
entire database goes to recovery mode and restarts, in the Postgres log, we
can find the below messages.
"2022-10-06 17:44:09.210 CEST [8860] LOG: server process (PID 9980) exited
with exit code 0
2022-10-06 17:44:09.210 CEST [8860] LOG: terminating any other active
server processes
2022-10-06 17:44:09.211 CEST [9992] WARNING: terminating the connection
because of the crash of another server process
2022-10-06 17:44:09.211 CEST [9992] 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.
2022-10-06 17:44:09.211 CEST [9992] HINT: In a moment you should be able to
reconnect to the database and repeat your command. "
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, sujeet.chaurasia@lisec.com
Subject: Re: BUG #17636: terminating connection because of crash of another server process
In-Reply-To: <17636-e10e2465ca1f6a74@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox