Re: BUG #18428: Connection broken but DB service still alive. - Mailing list pgsql-bugs

From 盧致均(Harry)
Subject Re: BUG #18428: Connection broken but DB service still alive.
Date
Msg-id CAPe_R0bHSaQ1VBKRSuQpSDWjc8LmNnefKyDt5jjY6T6aty6ywg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18428: Connection broken but DB service still alive.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi Tom,

It there a log path can record the shutdown signal is from where?
Because our postgresql server just provide for one web application to use.
And our test environment never happen this issue with same web application & DB version.

Tom Lane <tgl@sss.pgh.pa.us> 於 2024年4月12日 週五 下午9:38寫道:
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


--
Thank you & Best Regards

Harry Lu

______________________________________

Linktech Inc.

220 新北市板橋區三民路2段37號7樓之2
Phone:+886-2-2959-9166#160+886-2-7752-7658#160
E-mail: harry@linktech.com.tw
Web: www.linktech.com.tw

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: BUG #18411: Unable to create database with owner on AWS RDS
Next
From: Tender Wang
Date:
Subject: Re: BUG #18377: Assert false in "partdesc->nparts >= pinfo->nparts", fileName="execPartition.c", lineNumber=1943