Re: BUG #15101: function set search_path = '' breaks dump/restore

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15101: function set search_path = '' breaks dump/restore
Date: 2018-03-08 08:54:56
Message-ID: 876067kl4j.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "PG" == PG Bug reporting form <noreply(at)postgresql(dot)org> writes:

PG> Given:

PG> create or replace function foo()
PG> returns text language sql
PG> as $$
PG> select current_schemas(true)::text;
PG> $$
PG> set search_path = '';

For the record, the workaround I suggested to the user on IRC who ran
into this issue was:

alter function foo() set search_path = pg_catalog;

which has (as far as I can tell) exactly the same runtime effect as
setting it to '' but doesn't break dump/restore.

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Marius Vaičiulis 2018-03-08 11:45:42 9.6.7 -> 9.6.8 analyze worker behaviour changed?
Previous Message Michael Paquier 2018-03-08 08:19:55 Re: BUG #15101: function set search_path = '' breaks dump/restore