Re: No warning for a no-op REVOKE

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: No warning for a no-op REVOKE
Date: 2024-03-25 14:20:17
Message-ID: AF0FC716-ABC9-441F-BCB4-B4D510D228BA@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On 25 Mar 2024, at 15:09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> My initial reaction is that we should warn only when the command
> is a complete no-op, that is none of the mentioned privileges
> matched.

That's my gut reaction too,

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2024-03-25 14:37:45 Re: No warning for a no-op REVOKE
Previous Message Tom Lane 2024-03-25 14:09:42 Re: No warning for a no-op REVOKE