pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17666: Unexpected shutdown
2+ messages / 2 participants
[nested] [flat]

* BUG #17666: Unexpected shutdown
@ 2022-10-27 11:37 PG Bug reporting form <noreply@postgresql.org>
  2022-10-27 13:22 ` Re: BUG #17666: Unexpected shutdown Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Bug reporting form @ 2022-10-27 11:37 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: carlos.gonzalez@nologin.es

The following bug has been logged on the website:

Bug reference:      17666
Logged by:          Carlos Gonzalez
Email address:      carlos.gonzalez@nologin.es
PostgreSQL version: 11.13
Operating system:   Red Hat Enterprise Linux Server release 7.9 (Maipo
Description:        

Good morning,

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

Thank you very much



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: BUG #17666: Unexpected shutdown
  2022-10-27 11:37 BUG #17666: Unexpected shutdown PG Bug reporting form <noreply@postgresql.org>
@ 2022-10-27 13:22 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2022-10-27 13:22 UTC (permalink / raw)
  To: carlos.gonzalez@nologin.es; +Cc: pgsql-bugs@lists.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





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2022-10-27 13:22 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-10-27 11:37 BUG #17666: Unexpected shutdown PG Bug reporting form <noreply@postgresql.org>
2022-10-27 13:22 ` Tom Lane <tgl@sss.pgh.pa.us>

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