| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases |
| Date: | 2023-12-08 00:43:17 |
| Message-ID: | ZXJmpe__WfBZgKX2@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Nov 20, 2023 at 08:20:57PM -0700, David G. Johnston wrote:
> On Mon, Nov 20, 2023 at 8:16 PM Bruce Momjian <bruce(at)momjian(dot)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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-12-08 02:36:13 | Re: [DOCS] Confusing Trigger Docs. |
| Previous Message | Bruce Momjian | 2023-12-08 00:37:03 | Re: [DOCS] intagg.sgml: example wrongly named and does not compile |