Re: [HACKERS] Database variables when copying a database

2004-05-23 Thread Christopher Kings-Lynne
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. Good points. The reas

Re: [HACKERS] Database variables when copying a database

2004-05-23 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> 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 var

Re: [HACKERS] Database variables when copying a database

2004-05-22 Thread Christopher Kings-Lynne
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 cop

[HACKERS] Database variables when copying a database

2004-05-21 Thread Christopher Kings-Lynne
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