Date: Tue, 21 May 2013 21:42:49 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Robins Tharakan <tharakan@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: CREATE OPERATOR query
Message-ID: <20130522014249.GA15045@eldon.alvh.no-ip.org>
References: 
 <CAEP4nAw83qOywTH9STYCGxcGEZ+pjvSLN8Hyz_f-tZYODxVfHQ@mail.gmail.com>
	<CAEP4nAws7hm0xxgcd2MUEFZAvaw-stzcZ0RbnxA4=u0O2O-x=w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAEP4nAws7hm0xxgcd2MUEFZAvaw-stzcZ0RbnxA4=u0O2O-x=w@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Robins Tharakan escribió:
> Further, I seem to have a similar problem with the EXECUTE check
> requirement as well.
> Sample SQL given below.
> 
> BEGIN TRANSACTION;
> CREATE ROLE rol_op3;
> CREATE TYPE type_op3 AS ENUM ('new', 'open', 'closed');
> CREATE FUNCTION fn_op3(type_op3, type_op3)
> RETURNS type_op3 AS $$
>     SELECT NULL::type_op3;
> $$ LANGUAGE sql IMMUTABLE;
> REVOKE EXECUTE ON FUNCTION fn_op3(type_op3, type_op3) FROM rol_op3;

Doesn't PUBLIC still have EXECUTE permissions on this function?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs