On Mon, Sep 30, 2019 at 04:46:56PM +0900, Aramaki Zyake wrote:
> Hi,
>
> I’m terribly sorry for the delay of response.
>
>
>
> >This does not really seem like an improvement. The second formulation is
>
> >pedantically correct, but also unintelligible.
>
> >
>
> > Maybe we could make it say "run in parallel with non-DDL activity" ?
>
>
>
> I completely agree with you, therefore, I amended it as follows.
>
> ----
>
> ANALYZE requires only a read lock on the target table, so it can run in
>
> parallel with non-DDL activity on the table.
I know this report is four years old, but attached patch applied to
master.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml
index 4c79a01eb6..6ed8e7241b 100644
--- a/doc/src/sgml/ref/analyze.sgml
+++ b/doc/src/sgml/ref/analyze.sgml
@@ -208,7 +208,7 @@ ANALYZE [ ( <replaceable class="parameter">option</replaceable> [, ...] ) ] [ <r
<para>
<command>ANALYZE</command>
requires only a read lock on the target table, so it can run in
- parallel with other activity on the table.
+ parallel with other non-DDL activity on the table.
</para>
<para>
