I understand now; it wasn't the reading that was causing me problems it was figuring out the implications of the structure of the default privileges system. I suggest that ALTER DEFAULT PRIVILEGES (and probably REVOKE) raise a notice when attempting to REVOKE a [DEFAULT] PRIVILEGE that does not exist. Since I was issuing the REVOKE against the schema but the GRANT I was trying to revoke existed in GLOBAL there was nothing to revoke. If I had seen such a notice I would have realized (hopefully) that Global meant per-database and that it was my schema restriction that was causing the problem. Thanks again for helping me get my head around some of this stuff. David J -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Monday, February 14, 2011 7:05 PM To: David Johnston Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: Alter Default Privileges Does Not Work For Functions "David Johnston" <polobo@xxxxxxxxx> writes: > After creating and logging into a new database run this script. The > initial ALTER DEFAULT PRIVILEGES should make all users unable to > execute functions unless given explicit permissions elsewhere. You haven't read the fine manual very closely. It saith Default privileges that are specified per-schema are added to whatever the global default privileges are for the particular object type. and As explained under GRANT, the default privileges for any object type normally grant all grantable permissions to the object owner, and may grant some privileges to PUBLIC as well. However, this behavior can be changed by altering the global default privileges with ALTER DEFAULT PRIVILEGES. If you want to revoke the default execute privileges for functions, you have to do it globally, ie, not per-schema. There's no way to reduce the default privileges at the per-schema level. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
