Re: Moving test_fsync to /contrib?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving test_fsync to /contrib?
Date: 2011-01-17 17:05:54
Message-ID: 11503.1295283954@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Also, it's not going to get packaged at all unless it gets renamed to
something less generic, maybe pg_test_fsync; I'm not going to risk the
oppobrium of sticking something named "test_fsync" into /usr/bin.
Moving to contrib would be a good opportunity to fix the name.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2011-01-17 17:08:54 Re: REVIEW: Extensions support for pg_dump
Previous Message Cédric Villemain 2011-01-17 17:01:37 Re: Moving test_fsync to /contrib?