|From:||Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>|
|Subject:||Function to track shmem reinit time|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Attached patch introduces a new function pg_shmem_init_time(),
which returns the time shared memory was last (re)initialized.
It is created for use by monitoring tools to track backend crashes.
Currently, if the 'restart_after_crash' option is on, postgres will just
And the only way to know that it happened is to regularly parse logfile
or monitor it, catching restart messages. This approach is really
users, who have gigabytes of logs.
This new function can be periodiacally called by a monitoring agent, and,
if /shmem_init_time/ doesn't match /pg_postmaster_start_time,/
we know that server crashed-restarted, and also know the exact time, when.
Also, working on this patch, I noticed a bit of dead code
and some discordant comments in postmaster.c.
I see no reason to leave it as is.
So there is a small remove_dead_shmem_reinit_code_v0.patch.
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
|Next Message||Alexander Kuzmenkov||2018-02-28 12:55:19||Re: [patch] BUG #15005: ANALYZE can make pg_class.reltuples inaccurate.|
|Previous Message||David Rowley||2018-02-28 11:35:01||Re: [HACKERS] path toward faster partition pruning|