Re: archive_command / pg_stat_archiver & documentation

From: Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: archive_command / pg_stat_archiver & documentation
Date: 2021-03-02 08:07:46
Message-ID: CAPE8EZ5GW0AZ4fFZpHM1Qyw+90LmLL-ygptgEsR8SZkk8fE6Og@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks !

Le mar. 2 mars 2021 à 04:10, Julien Rouhaud <rjuju123(at)gmail(dot)com> a écrit :

> 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!
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nitin Jadhav 2021-03-02 08:37:12 Re: [PATCH] Bug fix in initdb output
Previous Message Dilip Kumar 2021-03-02 08:01:15 Re: [HACKERS] Custom compression methods