Re: Bug / shortcoming in has_*_privilege - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Bug / shortcoming in has_*_privilege
Date
Msg-id 1281513444.2142.1473.camel@ebony
Whole thread Raw
In response to Re: Bug / shortcoming in has_*_privilege  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug / shortcoming in has_*_privilege  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, 2010-06-10 at 23:18 -0400, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Thu, Jun 10, 2010 at 5:54 PM, Jim Nasby <jim@nasby.net> wrote:
> >> So there's no way to see if a particular privilege has been granted to public. ISTM 'public' should be accepted,
sinceyou can't use it as a role name anyway...
 
> 
> > It's a bit sticky - you could make that work for
> > has_table_privilege(name, oid, text) or has_table_privilege(name,
> > text, text), but what would you do about the versions whose first
> > argument is an oid?
> 
> Nothing.  The only reason to use those forms is in a join against
> pg_authid, and the "public" group doesn't have an entry there.

ISTM this bug should be on the open items list...

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: assertions and constraint triggers
Next
From: Vik Reykja
Date:
Subject: Re: Regression tests versus the buildfarm environment