From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adam FUCHS <atman@berkeley.edu>
cc: Korry Douglas <korry.douglas@enterprisedb.com>, pgsql-admin@postgresql.org
Subject: Re: postgres_fdw error
In-reply-to: 
 <CAG=eVo3kegHcW76bsRd+b+vUL1oACsfYbNo1t3Ld8-4hbb6JzQ@mail.gmail.com>
References: 
 <CAG=eVo2-1vnSEC+n1wmCi4744i=kurn=3J7fZPFH5zWd5NqXmQ@mail.gmail.com>
 <55CE4142.9030204@enterprisedb.com>
 <CAG=eVo3kegHcW76bsRd+b+vUL1oACsfYbNo1t3Ld8-4hbb6JzQ@mail.gmail.com>
Comments: In-reply-to Adam FUCHS <atman@berkeley.edu>
 message dated "Fri, 14 Aug 2015 14:19:21 -0700"
Date: Fri, 14 Aug 2015 17:38:49 -0400
Message-ID: <13868.1439588329@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Adam FUCHS <atman@berkeley.edu> writes:
> Thanks Korry, how would I check the search_path that is being used by the
> FDW user?

postgres_fdw always does "SET search_path = pg_catalog" when opening the
connection.  Probably this needs to be documented, since it's user-visible
if you try to attach a foreign table to a remote view.

Anyway the short answer is that you should fully schema-qualify references
in functions used by such a view, or else attach "SET search_path" options
to the functions.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin