Re: a raft of parallelism-related bug fixes
От | Noah Misch |
---|---|
Тема | Re: a raft of parallelism-related bug fixes |
Дата | |
Msg-id | 20151017233921.GA284904@tornado.leadboat.com обсуждение исходный текст |
Ответ на | Re: a raft of parallelism-related bug fixes (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: a raft of parallelism-related bug fixes
|
Список | pgsql-hackers |
On Sat, Oct 17, 2015 at 06:17:37PM -0400, Robert Haas wrote: > One idea that I think would provide > *excellent* test coverage is to take the test code included on this > thread and run it on the buildfarm. The idea of the code is to > basically run the regression test suite with every parallel-eligible > query forced to unnecessarily use parallelism. Turning that and > running 'make check' found, directly or indirectly, all of these bugs. > Doing that on the whole buildfarm would probably find more. > > However, I'm pretty sure that we don't want to switch the *entire* > buildfarm to using lots of unnecessary parallelism. What we might be > able to do is have some critters that people spin up for this precise > purpose. Just like we currently have CLOBBER_CACHE_ALWAYS buildfarm > members, we could have GRATUITOUSLY_PARALLEL buildfarm members. If > Andrew is willing to add buildfarm support for that option and a few What, if anything, would this mode require beyond adding a #define? If nothing, it won't require specific support in the buildfarm script. CLOBBER_CACHE_ALWAYS has no specific support. > people are willing to run critters in that mode, I will be happy - > more than happy, really - to put the test code into committable form, > guarded by a #define, and away we go. I would make one such animal.
В списке pgsql-hackers по дате отправления: