Re: Upcoming re-releases - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Upcoming re-releases
Date
Msg-id e51f66da0602100148w6e1deb39ke85ee7a0599ce536@mail.gmail.com
Whole thread Raw
In response to Re: Upcoming re-releases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2/9/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > Maybe this should be a configure flag, just like the port number is.
>
> It is ... that isn't the issue, the problem is exactly that Debian
> chooses to exercise the option to make their installations different
> from everyone else's.

It is exatly distributor's job to give consistent system.  I would
not like to use a distro that just does './configure;make;make install'
without any overview.

Especially considering that upstream defaults are bad.

OTOH as upstream job is _not_ to care about consistent system
- as it is not possible - then for upstream the backwards compatibility
is the most important thing.  It is likely that PostgreSQL upstream can
move the default only when most distros have already changed to sane
setting.

Oh, and I personally like that self-compiled PostgreSQL defaults to
other locations than system one.  Lessens danger of using experimental
stuff on useful data.

--
marko


pgsql-hackers by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: FW: PGBuildfarm member snake Branch HEAD Status changed from OK to ContribCheck failure
Next
From: Teodor Sigaev
Date:
Subject: Re: FW: PGBuildfarm member snake Branch HEAD Status changed