pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedLOCK docs and permissions
3+ messages / 3 participants
[nested] [flat]
* LOCK docs and permissions
@ 2024-04-05 10:25 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2024-04-05 10:25 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: jens.troeger@light-speed.de
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/explicit-locking.html
Description:
Hello,
It appears that LOCK on a schema.table requires particular permissions but I
can’t find which ones need to be granted in a schema.table in order to lock
said table.
I think it would help to add a short blurb on that?
Thank you!
Jens
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: LOCK docs and permissions
@ 2024-04-05 12:09 Laurenz Albe <laurenz.albe@cybertec.at>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: Laurenz Albe @ 2024-04-05 12:09 UTC (permalink / raw)
To: jens.troeger@light-speed.de; pgsql-docs@lists.postgresql.org
On Fri, 2024-04-05 at 10:25 +0000, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/16/explicit-locking.html
> Description:
>
> It appears that LOCK on a schema.table requires particular permissions but I
> can’t find which ones need to be granted in a schema.table in order to lock
> said table.
>
> I think it would help to add a short blurb on that?
https://www.postgresql.org/docs/current/sql-lock.html#id-1.9.3.155.7
"To lock a table, the user must have the right privilege for the specified
lockmode, or be the table's owner or a superuser. If the user has UPDATE,
DELETE, or TRUNCATE privileges on the table, any lockmode is permitted.
If the user has INSERT privileges on the table, ROW EXCLUSIVE MODE
(or a less-conflicting mode as described in Section 13.3) is permitted.
If a user has SELECT privileges on the table, ACCESS SHARE MODE is permitted."
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: LOCK docs and permissions
@ 2024-04-05 12:12 Jens <jens.troeger@light-speed.de>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 3+ messages in thread
From: Jens Tröger @ 2024-04-05 12:12 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-docs@lists.postgresql.org
Thank you, Laurenz, I missed that completely 🤦🏻♂️
Jens
> https://www.postgresql.org/docs/current/sql-lock.html#id-1.9.3.155.7
>
> "To lock a table, the user must have the right privilege for the specified
> lockmode, or be the table's owner or a superuser. If the user has UPDATE,
> DELETE, or TRUNCATE privileges on the table, any lockmode is permitted.
> If the user has INSERT privileges on the table, ROW EXCLUSIVE MODE
> (or a less-conflicting mode as described in Section 13.3) is permitted.
> If a user has SELECT privileges on the table, ACCESS SHARE MODE is permitted."
>
> Yours,
> Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2024-04-05 12:12 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-04-05 10:25 LOCK docs and permissions PG Doc comments form <noreply@postgresql.org>
2024-04-05 12:09 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-04-05 12:12 ` Jens <jens.troeger@light-speed.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox