| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | carlos(dot)gonzalez(at)nologin(dot)es |
| Subject: | BUG #17666: Unexpected shutdown |
| Date: | 2022-10-27 11:37:20 |
| Message-ID: | 17666-ebd96b17b269faa1@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17666
Logged by: Carlos Gonzalez
Email address: carlos(dot)gonzalez(at)nologin(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-10-27 12:31:22 | Re: BUG #17664: The subsctring() function with the char() text type does not work correctly |
| Previous Message | PG Bug reporting form | 2022-10-27 10:42:52 | BUG #17665: pg_stat_statements useless with variable number of parameters in IN close |