Re: Patch for 9.1: initdb -C option
От
Bruce Momjian
Тема
Re: Patch for 9.1: initdb -C option
Дата
Msg-id
201003312001.o2VK17m13124@momjian.us
Ответ на
Patch for 9.1: initdb -C option (David Christensen)
Список
Дерево обсуждения
Patch for 9.1: initdb -C option David Christensen <david@endpoint.com>
Re: Patch for 9.1: initdb -C option Peter Eisentraut <peter_e@gmx.net>
Re: Patch for 9.1: initdb -C option Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>
Re: Patch for 9.1: initdb -C option Bruce Momjian <bruce@momjian.us>
Re: Patch for 9.1: initdb -C option Greg Smith <greg@2ndquadrant.com>
Re: Patch for 9.1: initdb -C option KaiGai Kohei <kaigai@ak.jp.nec.com>
Re: Patch for 9.1: initdb -C option "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Patch for 9.1: initdb -C option David Christensen <david@endpoint.com>
Re: Patch for 9.1: initdb -C option "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Patch for 9.1: initdb -C option KaiGai Kohei <kaigai@ak.jp.nec.com>
Re: Patch for 9.1: initdb -C option Robert Haas <robertmhaas@gmail.com>
Re: Patch for 9.1: initdb -C option KaiGai Kohei <kaigai@ak.jp.nec.com>
Re: Patch for 9.1: initdb -C option Robert Haas <robertmhaas@gmail.com>
Re: Patch for 9.1: initdb -C option KaiGai Kohei <kaigai@ak.jp.nec.com>
Re: Patch for 9.1: initdb -C option Robert Haas <robertmhaas@gmail.com>
Re: Patch for 9.1: initdb -C option David Christensen <david@endpoint.com>
Re: Patch for 9.1: initdb -C option "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Patch for 9.1: initdb -C option Euler Taveira de Oliveira <euler@timbira.com>
I have added this to the 9.1 commit-fest: https://commitfest.postgresql.org/action/commitfest_view?id=6 --------------------------------------------------------------------------- David Christensen wrote: > Hackers, > > Enclosed is a patch to add a -C option to initdb to allow you to easily append configuration directives to the generated postgresql.conf file for use in programmatic generation. In my case, I'd been creating multiple db clusters with a script and would have specific overrides that I needed to make. This patch fell out of the desire to make this a little cleaner. Please review and comment. > > From the commit message: > > This is a simple mechanism to allow you to provide explicit overrides > to any GUC at initdb time. As a basic example, consider the case > where you are programmatically generating multiple db clusters in > order to test various configurations: > > $ for cluster in 1 2 3 4 5 6; > > do initdb -D data$cluster -C "port = 1234$cluster" -C 'max_connections = 10' -C shared_buffers=1M; > > done > > A possible future improvement would be to provide some basic > formatting corrections to allow specificications such as -C 'port > 1234', -C port=1234, and -C 'port = 1234' to all be ultimately output > as 'port = 1234' in the final output. This would be consistent with > postmaster's parsing. > > The -C flag was chosen to be a mnemonic for "config". > > Regards, > > David > -- > David Christensen > End Point Corporation > david@endpoint.com > > > [ Attachment, skipping... ] [ Attachment, skipping... ] > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com
В списке pgsql-hackers по дате отправления