Re: dblink: give search_path

From: "Thiemo Kellner, NHC Barhufpflege" <thiemo(dot)kellner(at)gelassene-pferde(dot)biz>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: dblink: give search_path
Date: 2018-04-17 11:23:08
Message-ID: 20180417132308.11075gcbf98r0s0s@www.gelassene-pferde.biz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Zitat von Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:

> In addition to my previous suggestions:
>
> test=# SELECT public.dblink_connect('dbname=production ');
> dblink_connect
> ----------------
> OK
>
> test=# select * from public.dblink('show search_path') as
> t1(search_path text);
> search_path
> -------------
> main
>
> test=# select public.dblink_exec('set search_path=main,utility');
> dblink_exec
> -------------
> SET
> (1 row)
>
> test=# select * from public.dblink('show search_path') as
> t1(search_path text);
> search_path
> ---------------
> main, utility
>

Hi Adrian. Thanks for pointing this out. I wonder why I did not think
of it myself. However, I moved to a dedicated logging user such
avoiding this Problem. I also seems a clean solution that way.

--
+49 (0)1578-772 37 37
+41 (0)78 947 36 21
Öffentlicher PGP-Schlüssel:
http://pgp.mit.edu/pks/lookup?op=get&search=0x8F70EFD2D972CBEF

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thiemo Kellner 2018-04-17 11:23:18 Re: psql variable to plpgsql?
Previous Message Gao Jack 2018-04-17 09:12:10 RE: pg_dump to a remote server