| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Avoid parallel full and right join paths. |
| Date: | 2016-04-20 22:27:29 |
| Message-ID: | CAB7nPqQPOqi7PkBWCp+7LMgDaomSpHpvWEhWrPo_J+-_PGh=Tg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 21, 2016 at 7:13 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Wed, Apr 20, 2016 at 2:49 PM, Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-04-20 22:38:56 | PGCTLTIMEOUT in pg_regress, or skink versus the clock |
| Previous Message | Peter Geoghegan | 2016-04-20 22:13:46 | Re: Avoid parallel full and right join paths. |