Re: create database ... template = ... does not copy configuration parameters values - Mailing list pgsql-bugs

From Joe Van Dyk
Subject Re: create database ... template = ... does not copy configuration parameters values
Date
Msg-id CACfv+pJvFBEGRkS1OytwxVpDCpO2-g7ZHupSeAwoNf-0k-OKfQ@mail.gmail.com
Whole thread Raw
In response to Re: create database ... template = ... does not copy configuration parameters values  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
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.

pgsql-bugs by date:

Previous
From: soweasley@gmail.com
Date:
Subject: BUG #11336: libpq.dll: file not recognized
Next
From: Per Wigren
Date:
Subject: PostgreSQL 9.2.9 segfault (backtrace included)