Minor typo in 13.3.5. Advisory Locks
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/explicit-locking.html
Description:
After the code snippet in the 6th paragraph of 13.3.5. Advisory Locks
(https://www.postgresql.org/docs/current/explicit-locking.html#ADVISORY-LOCKS)
I believe there is a mistake in this sentence (I've surrounded it with
asterisks):
"In the above queries, the second *form* is dangerous because the
LIMIT...".
I believe that "form" in the above sentence is actually meant to be "from",
referencing the second line of code and its FROM clause in the snippet.
PG Doc comments form <noreply@postgresql.org> writes:
Page: https://www.postgresql.org/docs/15/explicit-locking.html
After the code snippet in the 6th paragraph of 13.3.5. Advisory Locks
(https://www.postgresql.org/docs/current/explicit-locking.html#ADVISORY-LOCKS)
I believe there is a mistake in this sentence (I've surrounded it with
asterisks):
"In the above queries, the second *form* is dangerous because the
LIMIT...".
I believe that "form" in the above sentence is actually meant to be "from",
referencing the second line of code and its FROM clause in the snippet.
No, I think "form" is exactly what was meant. Maybe we should have
said "second query" or something like that, though.
regards, tom lane
On 28 Mar 2023, at 22:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
PG Doc comments form <noreply@postgresql.org> writes:
Page: https://www.postgresql.org/docs/15/explicit-locking.html
After the code snippet in the 6th paragraph of 13.3.5. Advisory Locks
(https://www.postgresql.org/docs/current/explicit-locking.html#ADVISORY-LOCKS)
I believe there is a mistake in this sentence (I've surrounded it with
asterisks):"In the above queries, the second *form* is dangerous because the
LIMIT...".I believe that "form" in the above sentence is actually meant to be "from",
referencing the second line of code and its FROM clause in the snippet.No, I think "form" is exactly what was meant.
Agreed, I think that was the indended spelling.
Maybe we should have said "second query" or something like that, though.
Reading this section I agree that the mix of ok/danger in the same example can
be tad misleading though. Something like the attached is what I would prefer
as a reader.
--
Daniel Gustafsson
Attachments:
adv_lock_limit.diffapplication/octet-stream; name=adv_lock_limit.diff; x-unix-mode=0644Download+13-10
Daniel Gustafsson <daniel@yesql.se> writes:
Reading this section I agree that the mix of ok/danger in the same example can
be tad misleading though. Something like the attached is what I would prefer
as a reader.
I think in your rewrite, "this query" is dangling a bit because there's
several sentences more before the query actually appears. I suggest
ordering things more like:
expressions are evaluated. For example,
this query is dangerous because the
<literal>LIMIT</literal> is not guaranteed to be applied before the locking
function is executed:
<screen>
SELECT pg_advisory_lock(id) FROM foo WHERE id > 12345 LIMIT 100; -- danger!
</screen>
This might cause some locks to be acquired
that the application was not expecting, and hence would fail to
...
On the other hand, these queries are safe:
<screen>
SELECT pg_advisory_lock(id) FROM foo WHERE id = 12345; -- ok
...
Separately from that: now that I look at this example, it's really
quite safe for any plausible plan shape. It used to be dangerous if
you had an ORDER BY, but there's no ORDER BY, and even if there were
we fixed that in 9118d03a8. Do we want to choose another example, and
if so what? The "not guaranteed" wording isn't really wrong, but an
example that doesn't do what we're saying it does isn't good either.
regards, tom lane
On 31 Mar 2023, at 14:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Daniel Gustafsson <daniel@yesql.se> writes:
Reading this section I agree that the mix of ok/danger in the same example can
be tad misleading though. Something like the attached is what I would prefer
as a reader.I think in your rewrite, "this query" is dangling a bit because there's
several sentences more before the query actually appears. I suggest
ordering things more like:expressions are evaluated. For example,
this query is dangerous because the
<literal>LIMIT</literal> is not guaranteed to be applied before the locking
function is executed:
<screen>
SELECT pg_advisory_lock(id) FROM foo WHERE id > 12345 LIMIT 100; -- danger!
</screen>
This might cause some locks to be acquired
that the application was not expecting, and hence would fail to
...
On the other hand, these queries are safe:
<screen>
SELECT pg_advisory_lock(id) FROM foo WHERE id = 12345; -- ok
...
Yes, I like this version a lot better than what I proposed.
Separately from that: now that I look at this example, it's really
quite safe for any plausible plan shape. It used to be dangerous if
you had an ORDER BY, but there's no ORDER BY, and even if there were
we fixed that in 9118d03a8. Do we want to choose another example, and
if so what? The "not guaranteed" wording isn't really wrong, but an
example that doesn't do what we're saying it does isn't good either.
Off the cuff I don't have any better suggestions, need to do some more
thinking.
--
Daniel Gustafsson