| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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-03 13:13:09 |
| Message-ID: | 20210303131309.xuasyj5kwwa5benh@nol |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 03, 2021 at 07:37:02AM -0500, David Steele wrote:
> On 3/1/21 8:29 PM, Michael Paquier 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.
>
> This was applied (except for a small part). Should we now consider this
> committed?
>
I think that we should consider this as committed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2021-03-03 13:21:37 | Re: Huge memory consumption on partitioned table with FKs |
| Previous Message | Andrew Dunstan | 2021-03-03 12:57:27 | Re: buildfarm windows checks / tap tests on windows |