From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Moving test_fsync to /contrib? |
Date: | 2011-01-17 16:47:40 |
Message-ID: | 201101171647.p0HGlev06993@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Mon, Jan 17, 2011 at 11:02 AM, Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-01-17 16:51:33 | Re: Moving test_fsync to /contrib? |
Previous Message | Christian Ullrich | 2011-01-17 16:46:59 | Re: SSPI client authentication in non-Windows builds |