Re: archive_command / pg_stat_archiver & documentation
Benoit Lobréau <benoit.lobreau@gmail.com>
From: Benoit Lobréau <benoit.lobreau@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Julien Rouhaud <rjuju123@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-01T08:33:48Z
Lists: pgsql-hackers
Le lun. 1 mars 2021 à 08:36, Michael Paquier <michael@paquier.xyz> a écrit : > On Fri, Feb 26, 2021 at 10:03:05AM +0100, Benoit Lobréau wrote: > > Done here : https://commitfest.postgresql.org/32/3012/ > > Documenting that properly for the archive command, as already done for > restore_command, sounds good to me. I am not sure that there is much > point in doing a cross-reference to the archiving section for one > specific field of pg_stat_archiver. > I wanted to add a warning that using pg_stat_archiver to monitor the good health of the archiver comes with a caveat in the view documentation itself. But couldn't find a concise way to do it. So I added a link. If you think it's unnecessary, that's ok. > For the second paragraph, I would recommend to move that to a > different <para> to outline this special case, leading to the > attached. > Good.
Commits
-
doc: Mention archive_command failure handling on signals
- 8c1b6a186d42 14.0 landed