Re: search_path when restoring to new db

From: Richard Huxton <dev(at)archonet(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Brandon Aiken <BAiken(at)winemantech(dot)com>, SunWuKung <Balazs(dot)Klein(at)t-online(dot)hu>, pgsql-general(at)postgresql(dot)org
Subject: Re: search_path when restoring to new db
Date: 2006-12-12 16:27:02
Message-ID: 457ED856.4080906@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
>> True enough, but I'd think you could make a good argument that dumping a
>> database should dump any ALTER commands that are attached to it.
>
> Let's suppose pg_dump did that, so "pg_dump foo >foo.dump" includes
> commands like
>
> ALTER DATABASE foo SET ...
>
> Now what happens when you try to load the script in database bar?
> Nothing very good ...

Which would point to the need to allow "ALTER DATABASE
current_database()" or similar I'd say.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Belinda M. Giardine 2006-12-12 16:32:47 date comparisons
Previous Message Merlin Moncure 2006-12-12 16:19:30 Re: PostgreSQL Developer Full-time Position