| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | curtis(at)mashedkeyboard(dot)me |
| Subject: | ALTER POLICY etc locks |
| Date: | 2023-09-20 08:37:44 |
| Message-ID: | 169519906452.3727334.8116461996527468040@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-alterpolicy.html
Description:
Hi folks, just wanted to drop a documentation suggestion: we document that
e.g. ALTER TABLE acquires an ACCESS EXCLUSIVE lock most of the time, but
there's currently no documentation that shows that ALTER POLICY does the
same. This seems to apply to the other POLICY commands too. It makes sense
as a behaviour, but could probably use writing down for clarity!
Source reference:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/commands/policy.c;hb=HEAD#l363
Cheers,
Curtis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-09-20 08:52:51 | Re: Typo/wording on https://www.postgresql.org/docs/current/catalog-pg-class.html |
| Previous Message | PG Doc comments form | 2023-09-20 05:23:19 | Typo/wording on https://www.postgresql.org/docs/current/catalog-pg-class.html |