Re: BUG #14192: pg_dump/pg_restore omit setting search_path in restored db

From: John R Pierce <pierce(at)hogranch(dot)com>
To: Hans Buschmann <buschmann(at)nidsa(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14192: pg_dump/pg_restore omit setting search_path in restored db
Date: 2016-06-15 15:48:35
Message-ID: bb66f4a9-ca80-c3c6-7e1c-99ede46ec844@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 6/15/2016 8:49 AM, Hans Buschmann wrote:
>
> Even the syntax (ALTER DATABASE xxxdb SET SEARCH PATH) suggests this
> to be part of the database and not of a session or the cluster.

that syntax is indeed stored with the database schema, and would be part
of a database dump.

you also can simply SET search_path 'somevalue'; and this applies
only to the current session, and wouldn't be part of the database

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hans Buschmann 2016-06-15 15:49:58 Re: BUG #14192: pg_dump/pg_restore omit setting search_path in restored db
Previous Message David G. Johnston 2016-06-15 15:47:39 Re: BUG #14192: pg_dump/pg_restore omit setting search_path in restored db