create database ... template = ... does not copy configuration parameters values

Started by Alexey Bashtanovabout 12 years ago4 messagesbugs
Jump to latest
#1Alexey Bashtanov
bashtanov@imap.cc

Hello!

There is a problem CREATE DATABASE does not copy configuration
parameters values:

[ACTIONS]
ui_dev_12=# create database bash_test;
CREATE DATABASE
ui_dev_12=# alter database bash_test set log_min_messages TO 'debug5';
ALTER DATABASE
ui_dev_12=# create database bash_test2 template = bash_test;
CREATE DATABASE
ui_dev_12=# \q
$ psql bash_test2
psql (9.3.1)
Type "help" for help.

bash_test2=# show log_min_messages;

[EXPECTED]
log_min_messages
------------------
debug5
(1 row)

[RECIEVED]
log_min_messages
------------------
warning
(1 row)

Please could you ether fix this behavior or at least describe current
behavior in docs.

Regards,
Alexey Bashtanov

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Alexey Bashtanov
bashtanov@imap.cc
In reply to: Alexey Bashtanov (#1)
Re: create database ... template = ... does not copy configuration parameters values

sorry
affects v.9.3.1 linux

On 17.02.2014 12:36, Alexey Bashtanov wrote:

Hello!

There is a problem CREATE DATABASE does not copy configuration
parameters values:

[ACTIONS]
ui_dev_12=# create database bash_test;
CREATE DATABASE
ui_dev_12=# alter database bash_test set log_min_messages TO 'debug5';
ALTER DATABASE
ui_dev_12=# create database bash_test2 template = bash_test;
CREATE DATABASE
ui_dev_12=# \q
$ psql bash_test2
psql (9.3.1)
Type "help" for help.

bash_test2=# show log_min_messages;

[EXPECTED]
log_min_messages
------------------
debug5
(1 row)

[RECIEVED]
log_min_messages
------------------
warning
(1 row)

Please could you ether fix this behavior or at least describe current
behavior in docs.

Regards,
Alexey Bashtanov

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#3Bruce Momjian
bruce@momjian.us
In reply to: Alexey Bashtanov (#1)
Re: create database ... template = ... does not copy configuration parameters values

On Mon, Feb 17, 2014 at 12:36:05PM +0400, Alexey Bashtanov wrote:

Hello!

There is a problem CREATE DATABASE does not copy configuration
parameters values:

[ACTIONS]
ui_dev_12=# create database bash_test;
CREATE DATABASE
ui_dev_12=# alter database bash_test set log_min_messages TO 'debug5';
ALTER DATABASE
ui_dev_12=# create database bash_test2 template = bash_test;
CREATE DATABASE
ui_dev_12=# \q
$ psql bash_test2
psql (9.3.1)
Type "help" for help.

bash_test2=# show log_min_messages;

[EXPECTED]
log_min_messages
------------------
debug5
(1 row)

[RECIEVED]
log_min_messages
------------------
warning
(1 row)

Please could you ether fix this behavior or at least describe
current behavior in docs.

I have applied the attached patch to document this limitation.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

Attachments:

template.difftext/x-diff; charset=us-asciiDownload+6-0
#4Joe Van Dyk
joe@tanga.com
In reply to: Bruce Momjian (#3)
Re: create database ... template = ... does not copy configuration parameters values

On Sat, Apr 19, 2014 at 12:27 PM, Bruce Momjian <bruce@momjian.us> wrote:

On Mon, Feb 17, 2014 at 12:36:05PM +0400, Alexey Bashtanov wrote:

Hello!

There is a problem CREATE DATABASE does not copy configuration
parameters values:

[ACTIONS]
ui_dev_12=# create database bash_test;
CREATE DATABASE
ui_dev_12=# alter database bash_test set log_min_messages TO 'debug5';
ALTER DATABASE
ui_dev_12=# create database bash_test2 template = bash_test;
CREATE DATABASE
ui_dev_12=# \q
$ psql bash_test2
psql (9.3.1)
Type "help" for help.

bash_test2=# show log_min_messages;

[EXPECTED]
log_min_messages
------------------
debug5
(1 row)

[RECIEVED]
log_min_messages
------------------
warning
(1 row)

Please could you ether fix this behavior or at least describe
current behavior in docs.

I have applied the attached patch to document this limitation.

Is there a reason for this? I would love for these types of variables to be
copied into backups, restored from dumps, etc.