Re: Database variables when copying a database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 17:02:09
Message-ID: 10418.1085245329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-05-22 18:14:42 Re: Database variables when copying a database
Previous Message Tom Lane 2004-05-22 16:52:39 Re: CVS HEAD: "make install" broken for vpath