Re: postgres_fdw, remote triggers and schemas - Mailing list pgsql-hackers

From Thom Brown
Subject Re: postgres_fdw, remote triggers and schemas
Date
Msg-id CAA-aLv6pSNvTvEtmpKK1iH5S-dS-jjdSsDiKfzWkmSuQkHEEtw@mail.gmail.com
Whole thread Raw
In response to Re: postgres_fdw, remote triggers and schemas  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 15 November 2013 21:03, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thom Brown <thom@linux.com> writes:
>> Is this unintended, or is it something users should fix themselves by
>> being explicit about relation schemas in trigger functions?  Should
>> the schema search path instead pick up whatever the default would be
>> for the user being used for the connection?
>
> postgres_fdw intentionally runs the remote session with a very minimal
> search_path (I think just pg_catalog, in fact).  I would argue that
> any trigger that breaks because of that is broken anyway, since it
> would fail --- possibly with security implications --- if some ordinary
> user modified the search path.

That makes sense.  Would it be worth putting a note in the
documentation about the behaviour of the search path on the
postgres_fdw page?

-- 
Thom



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: pg_dump insert with column names speedup
Next
From: Josh Berkus
Date:
Subject: Re: Turning recovery.conf into GUCs