Re: sqlsmith crash incremental sort

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: James Coleman <jtc331(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: sqlsmith crash incremental sort
Date: 2020-04-17 09:03:34
Message-ID: CAMbWs4_g7Ep1_WKM6MAtXeO5-AFNi91N+OxHGCiHBYc2x4JdzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 17, 2020 at 7:13 AM Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
wrote:

> On Thu, Apr 16, 2020 at 08:44:16PM +0200, Tomas Vondra wrote:
> >
> >Yeah, that's not entirely close to me. But maybe it shows us where we to
> >get the unprocessed target list?
> >
>
> I think at the very least this needs to apply the same change also to
> generate_nonunion_paths, because otherwise this fails because of the
> same issue:
>
> set enable_hashagg = off;
> explain select * from foo except select * from foo order by 1, 3;
>

Ah yes, that's what I'll have to do to cope with EXCEPT/INTERSECT.

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 曾文旌 2020-04-17 09:14:44 Re: [Proposal] Global temporary tables
Previous Message Jeremy Morton 2020-04-17 09:00:10 Re: Support for DATETIMEOFFSET