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

Re: Function's access control list ambiguity

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Dmitry Samokhin <sdld(at)mail(dot)ru>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Function's access control list ambiguity
Date: 2009-10-13 10:26:28
Message-ID: 937d27e10910130326g5aac2bb4j55b8c33900e6ac46@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-support
On Mon, Oct 5, 2009 at 12:48 PM, Dmitry Samokhin <sdld(at)mail(dot)ru> wrote:

> To implement this in case of empty, but not null, ACL of functions (and
> other database objects granting default access to PUBLIC), the
> reverse-engineering procedure of pgAdmin might be modified for the script to
> look like:
>
> CREATE OR REPLACE FUNCTION ... ;
> ALTER FUNCTION ... OWNER TO <owner>;
> REVOKE ALL ON FUNCTION ... FROM public;
> REVOKE ALL ON FUNCTION ... FROM <owner>;

Thanks, fixed in SVN for 1.10.1.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

In response to

pgadmin-support by date

Next:From: JohnDate: 2009-10-13 17:59:04
Subject: dropping connection
Previous:From: Dave PageDate: 2009-10-13 08:16:26
Subject: Re: PgAdmin iii

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