Re: Rework confusing permissions for LOCK TABLE

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rework confusing permissions for LOCK TABLE
Date: 2022-12-14 17:23:15
Message-ID: 20221214172315.GA689830@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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:

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-12-14 17:25:17 Re: Amcheck verification of GiST and GIN
Previous Message Nathan Bossart 2022-12-14 17:13:36 Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX