| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Jean-Denis Giguere <jdenisgiguere(at)fastmail(dot)fm>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: grant execute on many functions |
| Date: | 2004-06-30 03:45:14 |
| Message-ID: | 3318.1088567114@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Jean-Denis Giguere wrote:
>> But, the problem is more complex for functions because you have to give
>> the arguments.
> Does this help?
> SELECT n.nspname || '.' || p.proname ||
> '(' || pg_catalog.oidvectortypes(p.proargtypes) || ')'
Also, casting the function's OID to regprocedure may be useful.
Random example:
regression=# select 1142::regprocedure;
regprocedure
------------------------
date_mii(date,integer)
(1 row)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-06-30 04:20:02 | Re: grant execute on many functions |
| Previous Message | Tom Lane | 2004-06-30 03:37:22 | Re: How to list what queries are running in postgres? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-06-30 04:20:02 | Re: grant execute on many functions |
| Previous Message | Tom Lane | 2004-06-30 03:19:51 | Re: lock timeout patch |