| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgres_fdw vs. force_parallel_mode on ppc |
| Date: | 2016-02-15 23:12:03 |
| Message-ID: | 20160215231203.GD347322@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 15, 2016 at 06:07:48PM -0500, Tom Lane wrote:
> Noah Misch <noah(at)leadboat(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2016-02-15 23:23:43 | planstats.sgml |
| Previous Message | Tom Lane | 2016-02-15 23:07:48 | Re: postgres_fdw vs. force_parallel_mode on ppc |