Re: Avoid parallel full and right join paths. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Avoid parallel full and right join paths.
Date
Msg-id CAB7nPqQPOqi7PkBWCp+7LMgDaomSpHpvWEhWrPo_J+-_PGh=Tg@mail.gmail.com
Whole thread Raw
In response to Re: Avoid parallel full and right join paths.  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Avoid parallel full and right join paths.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Thu, Apr 21, 2016 at 7:13 AM, Peter Geoghegan <pg@heroku.com> wrote:
> On Wed, Apr 20, 2016 at 2:49 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> Committed.  But I think the regression test needs more thought, so I
>> left that out.
>
> It would be nice if there was a fuzz testing infrastructure that
> verified that parallel plans produce the same answer as serial plans.

Results of parallel plans and serial plans could be stored in
temporary tables in the test, then that's a matter of comparing them I
guess. That's largely doable.
-- 
Michael



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Avoid parallel full and right join paths.
Next
From: Tom Lane
Date:
Subject: PGCTLTIMEOUT in pg_regress, or skink versus the clock