dynamic monitoring

From: Brad DeJong <bpd0018(at)gmail(dot)com>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: dynamic monitoring
Date: 2025-02-21 18:17:51
Message-ID: CAJnrtnx6=KgQLn5nN5bXyPhurXFgTV4h6DU8E5tNGoFLiqG+yA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi all,

In the section on dynamic monitoring, I found the following
sentence confusing. I originally read it as "enclose the script"
and "used to allow that too to be checked" instead of "enclose
the script used" and "to allow that too to be checked".

When discussing information found using dynamic tracing,
be sure to enclose the script used to allow that too to be
checked and discussed.

Could it be rephrased as something like this?

When discussing information found using dynamic tracing,
be sure to enclose the script used to find the information
so that both the script and the information can be checked
and discussed.

Regards,
Brad

C:\src\postgresql\doc\src\sgml>git diff -p
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 71c4f96d05..d89261326a 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -7428,7 +7428,8 @@ Total time (ns) 2312105013
be meaningless. In most cases where problems are found it is the
instrumentation that is at fault, not the underlying system. When
discussing information found using dynamic tracing, be sure to enclose
- the script used to allow that too to be checked and discussed.
+ the script used to find that information so that both the script
+ and the information can be checked and discussed.
</para>
</sect2>

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2025-02-21 21:42:44 Re: Second paragraph a little bit misleading
Previous Message Bruce Momjian 2025-02-21 18:06:19 Re: Second paragraph a little bit misleading