Robert Haas wrote:
> 2010/9/27 Devrim G?ND?Z <devrim@gunduz.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@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +