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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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 14:16:14
Message-ID: 18195.1466000174@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

buschmann(at)nidsa(dot)net writes:
> On the origin database I had entered
> ALTER DATABASE xxxdb SET search_path TO public,partition2;
> The restore omits setting the search path, it must be entered again with
> ALTER DATABASE on the target machine.

This is operating as designed: pg_dump dumps the content of a database,
not settings attached to the database object as such. You can use
pg_dumpall (possibly with the -g switch) to capture that info.

There've been repeated discussions about refactoring this division of
labor, but nothing's been agreed to yet.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Joe Conway 2016-06-15 14:48:04 Re:
Previous Message digoal 2016-06-15 09:46:03 BUG #14193: cann't modify composite array's element in plpgsql?