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
Date: Thu, 27 Oct 2022 09:22:34 -0400
Message-ID: <642795.1666876954@sss.pgh.pa.us> (raw)
In-Reply-To: <17666-ebd96b17b269faa1@postgresql.org>
References: <17666-ebd96b17b269faa1@postgresql.org>
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
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, carlos.gonzalez@nologin.es, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17666: Unexpected shutdown
In-Reply-To: <642795.1666876954@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