From: Tom Lane <tgl@sss.pgh.pa.us>
To: carlos.gonzalez@nologin.es
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17666: Unexpected shutdown
In-reply-to: <17666-ebd96b17b269faa1@postgresql.org>
References: <17666-ebd96b17b269faa1@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 27 Oct 2022 11:37:20 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <642794.1666876954.1@sss.pgh.pa.us>
Date: Thu, 27 Oct 2022 09:22:34 -0400
Message-ID: <642795.1666876954@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/642795.1666876954%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Last October 2nd the postgresql service shut down the database
> unexpectedly.
> We only have this entry in the log file. Please, is there any way to
> investigate the problem with so little information?

> 2022-10-02 04:33:18.884 CDT pid: [9246] db:  user:  id: 6231c4b5.241e
> sqlstate: 00000 > LOG:  received immediate shutdown request

That is a commanded shutdown: something sent the postmaster process
a SIGQUIT signal.  The cause is very unlikely to be within Postgres
itself.  You should be thinking in terms of operator error or a
misbehaving administrative script.

			regards, tom lane