Skip site navigation (1) Skip section navigation (2)

Re: patch for type privileges

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: patch for type privileges
Date: 2011-12-01 21:19:04
Message-ID: 1322774344.23181.13.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On mån, 2011-11-28 at 14:25 -0600, Merlin Moncure wrote:
> On Tue, Nov 15, 2011 at 2:23 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > The basics here are mainly informed by the SQL standard.  One thing from
> > there I did not implement is checking for permission of a type used in
> > CAST (foo AS type).  This would be doable but relatively complicated,
> > and in practice someone how is not supposed to be able to use the type
> > wouldn't be able to create the cast or the underlying cast function
> > anyway for lack of access to the type.
> 
> I'm not quite following that: with your patch are you or are you not
> prohibited from utilizing casts?  In other words, if you didn't have
> USAGE priv, what would happen if you tried this:
> 
> CREATE VIEW v AS SELECT null::restricted_type::text; ?

This is not affected by my patch, so it would do whatever it did before.



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-12-01 22:43:33
Subject: Re: TupleDescInitEntry failing to initialize varlen members
Previous:From: Peter EisentrautDate: 2011-12-01 21:14:02
Subject: Re: patch for type privileges

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group