Re: postgres_fdw vs. force_parallel_mode on ppc
От | Noah Misch |
---|---|
Тема | Re: postgres_fdw vs. force_parallel_mode on ppc |
Дата | |
Msg-id | 20160215231203.GD347322@tornado.leadboat.com обсуждение исходный текст |
Ответ на | Re: postgres_fdw vs. force_parallel_mode on ppc (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: postgres_fdw vs. force_parallel_mode on ppc
|
Список | pgsql-hackers |
On Mon, Feb 15, 2016 at 06:07:48PM -0500, Tom Lane wrote: > Noah Misch <noah@leadboat.com> writes: > > I configured a copy of animal "mandrill" that way and launched a test run. > > The postgres_fdw suite failed as attached. A manual "make -C contrib > > installcheck" fails the same way on a ppc64 GNU/Linux box, but it passes on > > x86_64 and aarch64. Since contrib test suites don't recognize TEMP_CONFIG, > > check-world passes everywhere. > > Hm, is this with or without the ppc-related atomics fix you just found? Without those. The ppc64 GNU/Linux configuration used gcc, though, and the atomics change affects xlC only. Also, the postgres_fdw behavior does not appear probabilistic; it failed twenty times in a row.
В списке pgsql-hackers по дате отправления: