| From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Restart time indication in cases of postmaster initiated all backend restart |
| Date: | 2017-06-26 15:39:42 |
| Message-ID: | 87fuemzrk1.fsf@jsievers.enova.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Admins,
as per $subject, apart from server logs and/or client side diagnostics,
is there a way to query for event time when a crashed backend restart
happened?
Such an event does *not* result in postmaster itself restarting and thus
may lead to misleading confirmation of same.
DBAs may be inclined to select pg_postmaster_start_time() to confirm.
I have been aware of this fact for some time but I think less
experienced admins get thrown by it sometimes.
But to my question, is there some other function or equivalent method to
read this from inside the DB that I'm not aware of?
Thanks
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ghiureai | 2017-06-27 16:29:35 | PG container technologies which one ? |
| Previous Message | Ashish Tiwari | 2017-06-25 14:40:21 | Re: Re: pg9.6 - maintenance_work_mem is disabled in postgresql.conf by running a select query for pg_settings returns it is enabled |