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 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.
On Mon, Nov 20, 2023 at 8:16 PM Bruce Momjian 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_refe
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 th
On Mon, Nov 20, 2023 at 7:04 PM Bruce Momjian wrote:
> On Fri, Nov 17, 2023 at 03:44:04PM -0700, David G. Johnston wrote:
> > I don't like this particular solution to the stated complaint. When a
> FROM
> > entry has an alias it must be referenced via that alias anywhere it is
> > referenced in
On Fri, Nov 17, 2023 at 03:44:04PM -0700, David G. Johnston wrote:
> I don't like this particular solution to the stated complaint. When a FROM
> entry has an alias it must be referenced via that alias anywhere it is
> referenced in the query - and indeed it is an error to not write the alias in
>
On Fri, Nov 17, 2023 at 3:13 PM Bruce Momjian wrote:
> On Fri, Apr 27, 2018 at 01:47:49PM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.5/static/sql-select.html
> > Description:
> >
> > In
On Fri, Apr 27, 2018 at 01:47:49PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/static/sql-select.html
> Description:
>
> In the SELECT statement page the argument type of the (FOR SHARE/UPDA
Hi David,
Thanks for responding.
> It is. "If specific tables are named in a locking clause, then only rows
> coming from those tables are locked;"
I see – thanks for pointing it out.
It would be good if this sentence actually referred to "OF" by name. The
section on locking clauses is long
On Thu, Dec 17, 2020 at 5:29 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/sql-select.html
> Description:
>
> The FOR UPDATE clause of the SELECT statement can be followed by an OF
> clause, but th
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/sql-select.html
Description:
The FOR UPDATE clause of the SELECT statement can be followed by an OF
clause, but this is never explained at all in the documentation, as far as I
can tell. W
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/sql-select.html
Description:
In the SELECT statement page the argument type of the (FOR SHARE/UPDATE) OF
clause is listed to be a table_name. This is not *quite* accurate - it
shou
11 matches
Mail list logo
