From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: curtis@mashedkeyboard.me
Subject: ALTER POLICY etc locks
Date: Wed, 20 Sep 2023 08:37:44 +0000
Message-ID: <169519906452.3727334.8116461996527468040@wrigleys.postgresql.org> (raw)
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#l...
Cheers,
Curtis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, curtis@mashedkeyboard.me
Subject: Re: ALTER POLICY etc locks
In-Reply-To: <169519906452.3727334.8116461996527468040@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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