On Sat, 2013-09-07 at 14:01 -0400, Bruce Momjian wrote:
pg_has_role(n.nspowner, 'USAGE')
OR has_schema_privilege(n.oid, 'CREATE, USAGE')
As things stand, a non-superuser won't see public, pg_catalog,
nor even information_schema itself in this view, which seems a
tad
On Thu, Jan 31, 2013 at 03:49:36PM -0500, Peter Eisentraut wrote:
On 1/9/13 8:56 PM, Tom Lane wrote:
However, it seems to me that this behavior is actually wrong for our
purposes, as it represents a too-literal reading of the spec. The SQL
standard has no concept of privileges on schemas,
On 1/9/13 8:56 PM, Tom Lane wrote:
However, it seems to me that this behavior is actually wrong for our
purposes, as it represents a too-literal reading of the spec. The SQL
standard has no concept of privileges on schemas, only ownership.
We do have privileges on schemas, so it seems to me
2013/1/15 Tom Lane t...@sss.pgh.pa.us:
Casey Allen Shobe ca...@shobe.info writes:
On Wed, Jan 9, 2013 at 8:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
However, it seems to me that this behavior is actually wrong for our
purposes, as it represents a too-literal reading of the spec. The SQL
On Wed, Jan 9, 2013 at 8:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
However, it seems to me that this behavior is actually wrong for our
purposes, as it represents a too-literal reading of the spec. The SQL
standard has no concept of privileges on schemas, only ownership.
We do have
Casey Allen Shobe ca...@shobe.info writes:
On Wed, Jan 9, 2013 at 8:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
However, it seems to me that this behavior is actually wrong for our
purposes, as it represents a too-literal reading of the spec. The SQL
standard has no concept of privileges on
