Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY

From: Martijn van Oosterhout <kleptog(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
Date: 2022-08-04 14:41:11
Message-ID: CADWG95sFE1RS34RLPjGdcud_zDnJO686fNh8Yd=XWOShukHmNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hoi Richard, Tom,

On Thu, 4 Aug 2022 at 05:16, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:

>
> Yeah, I tested in bc76f5ac4. Attached is a regression test I composed.
> I tested it locally and it can catch this bug before 1aa8dad41 and give
> the expected answer after 1aa8dad41.
>
>
It looks like the issue has been found, nice! So I'm wondering: which
release will this fix be included (so we can mark the workaround with an
end date).

Thanks in advance.
--
Martijn van Oosterhout <kleptog(at)gmail(dot)com> http://svana.org/kleptog/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-08-04 14:56:32 BUG #17571: PostgreSQL 15b2 ICU collation defined at db level sorts differently in collate clause vs implicit
Previous Message Amit Kapila 2022-08-04 12:47:07 Re: Excessive number of replication slots for 12->14 logical replication