Patch - yes, a good way. but 1) requires invasion to the makefile 2)
makes changes in the file stored on git..
in case postgresql.conf.sample.in is a template, there are no such
problems. and this does not bother those who if someone assumes the
existence of the postgres.conf.sample file
>Even m
"Ivan N. Taranov" writes:
> 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 ..)
I'm with Peter on this: you're proposing to co
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
wrote:
>
> On 2020-03-28 10:00,
On 2020-03-28 10:00, i.tara...@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:
ar 2020 22:27:08 +0300
Subject: [PATCH] postgresql.conf.sample->postgresql.conf.sample.in
diff --git a/configure.in b/configure.in
index ecdf172396..c20992be77 100644
--- a/configure.in
+++ b/configure.in
@@ -2389,7 +2389,7 @@ fi
AC_SUBST(vpath_build)
-AC_CONFIG_FILES([GNUmakefile
