From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Moving test_fsync to /contrib? |
Date: | 2011-01-17 17:46:39 |
Message-ID: | 201101171746.p0HHkdt18891@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Mon, Jan 17, 2011 at 12:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >> On Mon, Jan 17, 2011 at 11:47 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >>> It seems like /contrib would be more natural, no? ?/bin seems like
> >>> overkill because most people will not want to run it. ?Most of /contrib
> >>> is installed already by installers, I think.
> >
> >> At least on Red Hat, it is packaged separately.
> >
> > 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?
I was suggesting /contrib because it seems to be of limited usefulness.
I assume people want pg_upgrade to stay in /contrib for the same reason.
--
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 | Tom Lane | 2011-01-17 17:48:34 | Re: Moving test_fsync to /contrib? |
Previous Message | Bruce Momjian | 2011-01-17 17:45:34 | Re: Moving test_fsync to /contrib? |