From: Tom Lane <tgl@sss.pgh.pa.us>
To: harry@linktech.com.tw
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18428: Connection broken but DB service still alive.
Date: Fri, 12 Apr 2024 09:38:21 -0400
Message-ID: <425283.1712929101@sss.pgh.pa.us> (raw)
In-Reply-To: <18428-93f18f22a86a84ce@postgresql.org>
References: <18428-93f18f22a86a84ce@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> 2024-04-06 13:54:53.868 CST [4840] LOG: received fast shutdown request
Something is sending your postmaster a shutdown signal (SIGINT).
You need to figure out how that is happening.
In the Windows world I think the most likely theory is that some
script is mistakenly issuing "pg_ctl stop"; the signal mechanism
we use on that platform doesn't map onto anything else people would
commonly do. But that's a guess. There's no hard evidence about
the signal source here.
regards, tom lane
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: tgl@sss.pgh.pa.us, harry@linktech.com.tw, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18428: Connection broken but DB service still alive.
In-Reply-To: <425283.1712929101@sss.pgh.pa.us>
* 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