Re: Required locks for ANALYZE

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Aramaki Zyake <zyake(dot)mk4(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Required locks for ANALYZE
Date: 2023-11-08 21:06:42
Message-ID: ZUv4Ytt-vVMSLrb8@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

Attachment Content-Type Size
analyze.diff text/x-diff 518 bytes

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2023-11-08 21:48:27 Re: readability changes to postgres.sgml
Previous Message Bruce Momjian 2023-11-08 17:42:02 Re: Version 14/15 documentation Section "Alter Default Privileges"