Postgres Pro
Downloads
Home   >   mailing lists

Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases - Mailing list pgsql-docs

From David G. Johnston
Subject Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases
Date
Msg-id CAKFQuwYVRJg9mdCSVKCdSpEoWnje9jxEiFfvOsX3Kr+_uG2NbA@mail.gmail.com
Whole thread Raw
In response to Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases  (Bruce Momjian <bruce@momjian.us>)
Responses Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases
List pgsql-docs
Tree view
On Mon, Nov 20, 2023 at 8:16 PM Bruce Momjian <bruce@momjian.us> wrote:
On Mon, Nov 20, 2023 at 07:19:39PM -0700, David G. Johnston wrote:
> The placement in the numbered listing section feels wrong, I am OK with
> the wording.  It should be down in the clause details.
>
> FOR lock_strength [ OF from_reference [, ...] ] [ NOWAIT | SKIP LOCKED ]  --
> need to change this spot to match
>
> where lock_strength can be one of
>
> [...]
>
> + and from_reference must be a table alias or non-hidden table_name referenced
> in the FROM clause.
>
> For more information on each [...]

Ah, good point.  I was searching for "FOR UPDATE" so I missed that
section;  updated patch attached.


WFM.

Thanks!

David J.

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases
Next
From: Bruce Momjian
Date:
Subject: Re: Documentation of FOR ROLE clause of ALTER DEFAULT PRIVILEGES missing