Re: Rework confusing permissions for LOCK TABLE - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Rework confusing permissions for LOCK TABLE
Date
Msg-id 20221214172315.GA689830@nathanxps13
Whole thread Raw
In response to Rework confusing permissions for LOCK TABLE  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Rework confusing permissions for LOCK TABLE  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Tue, Dec 13, 2022 at 06:59:48PM -0800, Jeff Davis wrote:
> I can't think of any reason for this behavior, and I didn't find an
> obvious answer in the last commits to touch that (2ad36c4e44,
> fa2642438f).

I can't think of a reason, either.

> Patch attached to simplify it. It uses the philosophy that, if you have
> permissions to lock at a given mode, you should be able to lock at
> strictly less-conflicting modes as well.

+1.  Your patch looks reasonable to me.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX
Next
From: Robert Haas
Date:
Subject: Re: Amcheck verification of GiST and GIN