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

From Bruce Momjian
Subject Re: Moving test_fsync to /contrib?
Date
Msg-id 201101171647.p0HGlev06993@momjian.us
Whole thread Raw
In response to Re: Moving test_fsync to /contrib?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Moving test_fsync to /contrib?  (Robert Haas <robertmhaas@gmail.com>)
Re: Moving test_fsync to /contrib?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Mon, Jan 17, 2011 at 11:02 AM, Bruce Momjian <bruce@momjian.us> wrote:
> >> Is there value in moving test_fsync to /contrib?
> 
> > Why would we want to do that?
> 
> So it would be built by default, installed under reasonable conditions,
> and there would be a place to document it.  Where it is, it's not a
> user-facing thing at all.

I have cleaned up the code so it is reasonable to ship and use by
end-users.  It is documented already where we mention setting
wal_sync_method, but having it in src/tools really is a hinderance.

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.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Christian Ullrich
Date:
Subject: Re: SSPI client authentication in non-Windows builds
Next
From: Robert Haas
Date:
Subject: Re: Moving test_fsync to /contrib?