Re: Moving test_fsync to /contrib?
От | Bruce Momjian |
---|---|
Тема | Re: Moving test_fsync to /contrib? |
Дата | |
Msg-id | 201101171647.p0HGlev06993@momjian.us обсуждение исходный текст |
Ответ на | Re: Moving test_fsync to /contrib? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Moving test_fsync to /contrib?
Re: Moving test_fsync to /contrib? |
Список | 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 по дате отправления: