Re: Database variables when copying a database - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Database variables when copying a database
Date
Msg-id 40AF06CC.5090107@familyhealth.com.au
Whole thread Raw
In response to Database variables when copying a database  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Database variables when copying a database  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: pg_autovacuum fixes
Next
From: Fabien COELHO
Date:
Subject: Re: postgresql extension API proof of concept