Re: archive_command / pg_stat_archiver & documentation
Benoit Lobréau <benoit.lobreau@gmail.com>
From: Benoit Lobréau <benoit.lobreau@gmail.com>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-02T08:07:46Z
Lists: pgsql-hackers
Thanks ! Le mar. 2 mars 2021 à 04:10, Julien Rouhaud <rjuju123@gmail.com> a écrit : > On Tue, Mar 2, 2021 at 9:29 AM Michael Paquier <michael@paquier.xyz> > wrote: > > > > 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. > > Thanks! >
Commits
-
doc: Mention archive_command failure handling on signals
- 8c1b6a186d42 14.0 landed