Re: Database variables when copying a database

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Database variables when copying a database
Date: 2004-05-22 07:52:44
Message-ID: 40AF06CC.5090107@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Anyone thought about this at all yet? Is it possible to have
per-database variables that refer to the current database in someway
that would need to be altered to refer to the new db?

Chris

Christopher Kings-Lynne wrote:
> Hi,
>
> When you do this:
>
> CREATE DATABASE test TEMPLATE master;
>
> It doesn't copy any per-database GUC variables, created by the ALTER
> DATABASE master SET var TO val; command.
>
> Should it?
>
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2004-05-22 08:59:31 Re: postgresql extension API proof of concept
Previous Message Matthew T. O'Connor 2004-05-22 07:47:56 pg_autovacuum fixes