From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PostgreSQL Hackers ML <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A small update for postgresql.conf.sample |
Date: | 2010-10-14 17:05:30 |
Message-ID: | 201010141705.o9EH5U113032@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> 2010/9/27 Devrim G?ND?Z <devrim(at)gunduz(dot)org>:
> > On Mon, 2010-09-27 at 09:40 -0400, Robert Haas wrote:
> >> > Actually, I don't see any reason why not to backpatch it.
> >>
> >> I was wondering if it would cause package management headaches for
> >> people who had already modified their postgresql.conf.
> >
> > We don't overwrite .conf files during upgrades.
>
> All right, have it your way. Done. :-)
>
> (Dang this is a lot easier than the old way.)
Uh, I have always been reluctant to backpatch changes to
postgresql.conf.sample because those changes are going to be installed
in share/postgresql.conf.sample during a minor upgrade. After that, if
someone diffs their data/postgresql.conf with
share/postgresql.conf.sample, they will see change that they did not
make to postgresql.conf.
Not sure you want to revert this changes, but I wanted to be sure people
understood this behavior.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-10-14 17:06:34 | commitfest timing |
Previous Message | Peter Eisentraut | 2010-10-14 17:03:26 | Re: duplicate connection failure messages |