From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | ps display "waiting for max_standby_delay" |
Date: | 2010-06-07 04:42:44 |
Message-ID: | 20100607134243.90DE.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
We have codes to change ps display for recovery process during hot standby.
The current code always shows max_standby_delay for the message, but how
about showing actual waiting time instead? Since DBAs can always get the
parameter from postgresql.conf they wrote, so the parameter value itself
is not so useful. Actual waiting time might be more useful to determine
which values to be set to max_standby_delay, no?
[backend/storage/ipc/standby.c]
snprintf(new_status + len, 50,
" waiting for max_standby_delay (%d ms)",
MaxStandbyDelay); ==> GetCurrentTimestamp() - waitStart
set_ps_display(new_status, false);
I think SQL-based activity view will be more useful than ps display,
but it's an item for 9.1.
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2010-06-07 04:59:02 | Re: [PATCH] Fix leaky VIEWs for RLS |
Previous Message | Stephen Frost | 2010-06-07 03:06:47 | Re: [PATCH] Fix leaky VIEWs for RLS |