Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1oJcYw-0007oT-3m
	for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Aug 2022 15:15:02 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1oJcYv-00065J-1F
	for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Aug 2022 15:15:01 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oJcYu-00065A-Pv
	for pgsql-bugs@lists.postgresql.org; Thu, 04 Aug 2022 15:15:00 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oJcYs-0001V5-9e
	for pgsql-bugs@lists.postgresql.org; Thu, 04 Aug 2022 15:15:00 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 274FEukR3503680;
	Thu, 4 Aug 2022 11:14:56 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@gmail.com>
cc: Richard Guo <guofenglinux@gmail.com>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17564: Planner bug in combination of generate_series(),
 unnest() and ORDER BY
In-reply-to: 
 <CADWG95sFE1RS34RLPjGdcud_zDnJO686fNh8Yd=XWOShukHmNg@mail.gmail.com>
References: <17564-c7472c2f90ef2da3@postgresql.org>
 <2184335.1659392231@sss.pgh.pa.us>
 <CADWG95s03YZsRy3+q0bQFXW_v_f-9vMvcFOo6KUL08DvqbXhqg@mail.gmail.com>
 <CAMbWs49AgGUophtyThqHhSUyDTu3h6oATg-7GgowCtvHWCh9qQ@mail.gmail.com>
 <3002973.1659538573@sss.pgh.pa.us>
 <CAMbWs4_W70RK77_j+_QzYAey2oQoxa8pwb0rp8KCeeH4bt5Jzg@mail.gmail.com>
 <3297011.1659578134@sss.pgh.pa.us>
 <CAMbWs49AAq1V18=n37qOmAdWOd0-Y=_Z6Wy1gWM2=FeqJWbrCQ@mail.gmail.com>
 <CADWG95sFE1RS34RLPjGdcud_zDnJO686fNh8Yd=XWOShukHmNg@mail.gmail.com>
Comments: In-reply-to Martijn van Oosterhout <kleptog@gmail.com>
	message dated "Thu, 04 Aug 2022 16:41:11 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3503678.1659626096.1@sss.pgh.pa.us>
Date: Thu, 04 Aug 2022 11:14:56 -0400
Message-ID: <3503679.1659626096@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/3503679.1659626096%40sss.pgh.pa.us>
Precedence: bulk

Martijn van Oosterhout <kleptog@gmail.com> writes:
> 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).

Next week's.

https://www.postgresql.org/developer/roadmap/

			regards, tom lane