Tatsuo Ishii <t-ishii@sra.co.jp> writes:
>> I believe the spec just demands USAGE on the underlying function for
>> the TRANSLATE case, and I don't see why it should be different for
>> CONVERT. (In principle, if we didn't use a C-only API, you could
>> just call the underlying function directly; so there's little point
>> in having protection restrictions different from that case.)
> Ok, so:
> (1) a CONVERSION can only be dropped by the superuser or its owner.
Okay ...
> (2) a grant syntax for CONVERSION is:
> GRANT USAGE ON CONVERSION <conversion_name> to
> {<user_name> | GROUP <group_name> | PUBLIC} [, ...]
No, I don't think a conversion has any privileges of its own at all.
You either have USAGE on the underlying function, or not.
regards, tom lane
