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

From Tom Lane
Subject Re: Database variables when copying a database
Date
Msg-id 10418.1085245329@sss.pgh.pa.us
Whole thread Raw
In response to Re: Database variables when copying a database  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Database variables when copying a database  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> Anyone thought about this at all yet?

It seems to me that we shouldn't copy them, but I'm having a hard time
putting a finger on why exactly.  I guess it goes along with the fact
that we don't copy the database's owner, and any per-database variable
settings seem to me to be the database owner's decision to make.

Also I refer you to the point made in the manual that CREATE DATABASE is
not intended to be a COPY DATABASE facility.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CVS HEAD: "make install" broken for vpath
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Database variables when copying a database