permission inconsistency with functions - Mailing list pgsql-hackers

From Joshua D. Drake
Subject permission inconsistency with functions
Date
Msg-id 1279910930.9866.19.camel@jd-desktop.iso-8859-1.charter.com
Whole thread Raw
List pgsql-hackers
Hello,

I am writing a blog on backups with postgresql, which I plan at some
point (if someone doesn't beat me to it) on turning into a patch for the
docs but I found this inconsistency:

The docs state that:

"In particular, it must have read access to all tables that you want to
back up, so in practice you almost always have to run it as a database
superuser."

Ignoring the fact that databases have a lot more objects than tables,
there is no READ/SELECT permission for functions. Thus in order to
backup a function, I must have EXECUTE permissions on the function.
Further if I don't have EXECUTE permissions I can still see the function
in pg_proc.

This seems like an inconsistency worth looking into, especially now that
we have per column perms. 

Sincerely,

Joshua D. Drake

-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Rewrite, normal execution vs. EXPLAIN ANALYZE
Next
From: "Joshua D. Drake"
Date:
Subject: Re: permission inconsistency with functions