BUG #17636: terminating connection because of crash of another server process

The following bug has been logged on the website:

Bug reference: 17636
Logged by: Sujeet Swaminath
Email address: sujeet(dot)chaurasia(at)lisec(dot)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. "