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.
In-reply-to: <18428-93f18f22a86a84ce@postgresql.org>
References: <18428-93f18f22a86a84ce@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 12 Apr 2024 08:14:28 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <425282.1712929101.1@sss.pgh.pa.us>
Date: Fri, 12 Apr 2024 09:38:21 -0400
Message-ID: <425283.1712929101@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/425283.1712929101%40sss.pgh.pa.us>
Precedence: bulk

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