At 2008-09-06 19:59:55 -0400, [EMAIL PROTECTED] wrote: > > So I'm thinking it would be better to invent a has_sequence_privilege > family of functions.
Perhaps. I certainly wouldn't object to that approach. If there had been such a function, I would have used it; and, since has_table_privilege doesn't help me in any released version, I have nothing invested in that way of doing things. (I can't help but think that the USAGE privilege is a bit unfortunate. If granting SELECT rights allowed currval(), INSERT allowed nextval(), and UPDATE allowed nextval() and setval(), then has_table_privilege() would have been sufficient and there would be no need to invent a new set of functions just to check USAGE. At the moment, however, I have to grant UPDATE instead of USAGE, both for compatibility with 8.1, and because there is no easy way to check if USAGE has already been granted, even though I don't want to allow setval() at all. Pity.) -- ams PS. I'm sorry I haven't been able to review any patches this time. I meant to, but a sequence of unfortunate events conspired to keep me busy elsewhere. I look forward to participating again next time. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
