| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 03:10:45 |
| Message-ID: | CAOBaU_a-YG-O=+DJx9dvvwnrVfeVfiVW_5F4ieeWU5LK-U2dtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 2, 2021 at 9:29 AM Michael Paquier <michael(at)paquier(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-03-02 03:25:29 | Re: 64-bit XIDs in deleted nbtree pages |
| Previous Message | Peter Geoghegan | 2021-03-02 03:00:41 | Re: New IndexAM API controlling index vacuum strategies |