| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | dipti shah <shahdipti1980(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: SET Role doesn't work from Security Definer Function... |
| Date: | 2010-02-23 15:06:39 |
| Message-ID: | 20100223150639.GD3672@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice |
dipti shah escribió:
> For your reference I did something like this:
>
> 1. Create Function foo1 .... (this is without SECURITY DEFINER where I am
> using SET ROLE to current user).
>
> 2. Create Function foo2 with SECURITY DEFINER ...
> spi_exe_query("select foo1()"); ==> Here it throws the error.
Shouldn't it be the other way around? The normal function calls the
security-definer one.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-23 15:47:29 | Re: pg_dump new version |
| Previous Message | Stefan Schwarzer | 2010-02-23 14:43:13 | Re: Subqueries or Joins? Problems with multiple table query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-23 15:53:55 | Re: Minor systax error but not able to resolve it... |
| Previous Message | Susan M Farley | 2010-02-23 14:58:45 | Function Error |