| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Subject: | Re: archive_command / pg_stat_archiver & documentation |
| Date: | 2021-03-03 12:37:02 |
| Message-ID: | 299b9263-4cd0-b38b-ba93-f5972be118f3@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
If not, can we get a new patch for the remaining changes?
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2021-03-03 12:50:22 | Re: [PATCH] Identify LWLocks in tracepoints |
| Previous Message | Ashutosh Bapat | 2021-03-03 12:21:31 | Re: Why OR-clauses not getting copied into baserestrictinfo of another table whose columns are in the same EquivalenceClass? |