| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: archive_command / pg_stat_archiver & documentation |
| Date: | 2021-03-02 01:29:41 |
| Message-ID: | YD2VBRvTa1v7fsq4@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 01, 2021 at 05:17:06PM +0800, Julien Rouhaud wrote:
> Maybe this can be better addressed than with a link in the
> documentation. The final outcome is that it can be difficult to
> monitor the archiver state in such case. That's orthogonal to this
> patch but maybe we can add a new "archiver_start" timestamptz column
> in pg_stat_archiver, so monitoring tools can detect a problem if it's
> too far away from pg_postmaster_start_time() for instance?
There may be other solutions as well. I have applied the doc patch
for now.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2021-03-02 01:31:06 | Re: TRIM_ARRAY |
| Previous Message | Michael Paquier | 2021-03-02 01:23:21 | Re: [PATCH] Bug fix in initdb output |