From: | "Ivan N(dot) Taranov" <i(dot)taranov(at)postgrespro(dot)ru> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in |
Date: | 2020-03-28 12:06:06 |
Message-ID: | CAKqLMA8rGdeDC9qsFTyQ-mCaTurOw99t23VCgf5BViZ_3q8MBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 2020-03-28 10:00, i(dot)taranov(at)postgrespro(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-03-28 12:18:58 | Re: Online checksums verification in the backend |
Previous Message | Sergei Kornilov | 2020-03-28 11:20:44 | Re: Allow some recovery parameters to be changed with reload |