| From: | Julie Nishimura <juliezain(at)hotmail(dot)com> |
|---|---|
| To: | |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | postgresql 9.4 restart |
| Date: | 2019-05-08 18:00:19 |
| Message-ID: | BYAPR08MB5014F151ACBD5FD717E1CACBAC320@BYAPR08MB5014.namprd08.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
Our staging 9.4 postgresql has been running couple of weeks with no problem, but yesterday we saw this error from one of our services that connects to the staging DBs:
FATAL: terminating connection due to
administrator command; nested exception is
org.postgresql.util.PSQLException: FATAL: terminating connection due to
administrator command”,
Then I could see that postgresql got restarted, based on the output of "select pg_postmaster_start_time()"
We are running postgresql on
Linux xxx-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
How I can find out what cause the restart? Any ideas are welcome. Thanks!
-Julie N
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-05-08 18:12:56 | Re: Query on pg_stat_activity table got stuck |
| Previous Message | neeraj kumar | 2019-05-08 17:42:12 | Re: Query on pg_stat_activity table got stuck |