Re: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in
От | Ivan N. Taranov |
---|---|
Тема | Re: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in |
Дата | |
Msg-id | CAKqLMA8rGdeDC9qsFTyQ-mCaTurOw99t23VCgf5BViZ_3q8MBA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in
|
Список | pgsql-hackers |
This is usable for build installable postgresql.conf.SAMPLE. At the configure phase, it is possible to include / exclude parameters in the sample depending on the selected options (--enable - * / - disable- * etc ..) On Sat, Mar 28, 2020 at 2:21 PM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > > On 2020-03-28 10:00, i.taranov@postgrespro.ru wrote: > > A patch for converting postgresql.conf.sample to > > postgresql.conf.sample.in . This feature allows you to manage the > > contents of postgresql.conf.sample at the configure phase. > > > > Usage example: > > > > ./configure --enable-foo > > > > > > configure.in: > > > > foo_params=$(cat <<-END > > foo_param1 = on > > foo_param2 = 16 > > END > > ) > > AC_SUBST(foo_params) > > > > > > postgresql.conf.sample.in: > > > > @foo_params@ > > > > > > postgresql.conf.sample: > > > > foo_param1 = on > > foo_param2 = 16 > > Why do we need that? We already have the capability to make initdb edit > postgresql.conf. > > -- > Peter Eisentraut http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: