From: | Adam FUCHS <atman(at)berkeley(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: postgres_fdw error |
Date: | 2015-08-18 23:50:37 |
Message-ID: | CAG=eVo1TLH7UdDk2YUdGpkWB1Z+wymz6K9=Rfg89AUeEi7zzNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I just wanted to update folks that indeed running this for each function
called in the view fixed my permissions issues:
ALTER FUNCTION <func> SET search_path=public;
I also had to grant select to the mapped user for each table used in the
function call.
Thank you for everyone's help!
Adam
On Sat, Aug 15, 2015 at 11:34 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Adam FUCHS <atman(at)berkeley(dot)edu> writes:
> > In case this breaks stuff, what is the default search_path for functions
> if
> > they are created without one set explicitly?
>
> Ordinarily a function just runs with whatever search_path is active
> when it's called.
>
> regards, tom lane
>
--
Adam Fuchs
Database Administrator
UC Berkeley - Information Services & Technology
2195 Hearst Ave., Berkeley, CA 94120
510-664-4354
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2015-08-20 17:52:51 | Re: FW: [webmaster] Security issue PostgreSQL problems VFE CZ |
Previous Message | Magnus Hagander | 2015-08-18 10:48:40 | Re: [webmaster] Security issue PostgreSQL problems VFE CZ |