From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adam FUCHS <atman@berkeley.edu>
Cc: Korry Douglas <korry.douglas@enterprisedb.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres_fdw error
Date: Fri, 14 Aug 2015 17:38:49 -0400
Message-ID: <13868.1439588329@sss.pgh.pa.us> (raw)
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, atman@berkeley.edu, korry.douglas@enterprisedb.com
Subject: Re: postgres_fdw error
In-Reply-To: <13868.1439588329@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox