From: Noah Misch <noah@leadboat.com>
To: Aya Iwata (Fujitsu) <iwata.aya@fujitsu.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
Date: Mon, 25 Nov 2024 18:17:13 -0800
Message-ID: <20241126021713.71.nmisch@google.com> (raw)
In-Reply-To: <OS7PR01MB119646C422A69AC5017A68BDBEA2E2@OS7PR01MB11964.jpnprd01.prod.outlook.com>
References: <OS7PR01MB11964507B5548245A7EE54E70EA212@OS7PR01MB11964.jpnprd01.prod.outlook.com>
<20241120062742.b0.nmisch@google.com>
<20241121011100.c3.nmisch@google.com>
<OS7PR01MB119646C422A69AC5017A68BDBEA2E2@OS7PR01MB11964.jpnprd01.prod.outlook.com>
On Mon, Nov 25, 2024 at 05:54:50AM +0000, Aya Iwata (Fujitsu) wrote:
> >Did you ever see the WARNING with a DATABASE command, or just with a
> >TABLESPACE command?
>
> We tried this, but there is no WARNING on GRANT xxx ON DATABASE command.
>
> But I did notice a warning while REVOKE xxx ON TABLESPACE.
>
> $ psql -x -p 5432 -d postgres -c "REVOKE CREATE ON TABLESPACE test_tbl_spc FROM nmluser1;"
> WARNING: you don't own a lock of type ExclusiveLock
> REVOKE
>
> So both GRANT and REVOKE command on TABLESPACE seems to throw an WARNING.
That makes sense. I've pushed postgr.es/c/4ba84de for this.
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-bugs@postgresql.org
Cc: noah@leadboat.com, iwata.aya@fujitsu.com, pgsql-bugs@lists.postgresql.org
Subject: Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
In-Reply-To: <20241126021713.71.nmisch@google.com>
* 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