Re: Moving test_fsync to /contrib? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Moving test_fsync to /contrib?
Date
Msg-id AANLkTin+tLPcW8t-21c1DNfxj6c58fjox8S_14+pMXc9@mail.gmail.com
Whole thread Raw
In response to Re: Moving test_fsync to /contrib?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jan 17, 2011 at 12:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Mon, Jan 17, 2011 at 12:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> On Red Hat, it is not packaged at all (at least not by me), and won't
>>> be unless it goes into contrib. I don't believe it belongs in the
>>> base package.
>
>> I confess to some confusion about what things "belong" where.  Is
>> contrib the right place for this because we think it's half-baked, or
>> because we think most people won't use it, or just because we're
>> violently allergic to adding stuff to src/bin, or what?
>
> The first two, if you ask me.  And there's another point: I disagree
> with the assumption that platform-specific packagings will or should
> include test_fsync by default.  It'd be better for the packager to make
> a platform-specific choice of default for the users.  I don't mind too
> much putting it into a secondary subpackage such as postgresql-contrib,
> but you won't be seeing it in postgresql-server.

I see.  Well, that seems reasonable.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Moving test_fsync to /contrib?
Next
From: Kääriäinen Anssi
Date:
Subject: Re: REVIEW: Extensions support for pg_dump