Peter Eisentraut <pete...@gmx.net> writes:
> On tis, 2009-09-01 at 12:04 -0500, Kevin Grittner wrote:
>> And unless I'm remembering incorrectly, the configure options are not
>> what we would want. I don't see any reason the packaged build
>> shouldn't be with --enable-debug on a platform where that has no
>> performance hit.
> Debatable, but it's not upstream default, so why should it be downstream
> default?
FWIW, that particular issue is invariably a matter of distro policy;
they could care less what upstream's default is. For instance Red Hat
*always* builds all RPMs with debug enabled, and then splits the debug
data off into separate "debuginfo" RPMs, which are not installed by
default for space/bandwidth reasons. But you can get debug symbols when
you need 'em. I don't know what Debian or SUSE do, but I'm sure they do
it consistently across all their packages. A lot of other packaging
choices are likewise driven by distro-wide policy and not what a
particular upstream package might choose as default.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
