Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1vbm4P-00CnSc-0n
	for pgsql-performance@arkaria.postgresql.org;
	Fri, 02 Jan 2026 20:48:26 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1vbm4M-00BBrs-2v
	for pgsql-performance@arkaria.postgresql.org;
	Fri, 02 Jan 2026 20:48:23 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vbm2b-00B86E-0F
	for pgsql-performance@lists.postgresql.org;
	Fri, 02 Jan 2026 20:46:33 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vbm2Z-0048YL-0h
	for pgsql-performance@postgresql.org;
	Fri, 02 Jan 2026 20:46:33 +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 602KkT00267808;
	Fri, 2 Jan 2026 15:46:30 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: wotq <wotq@wotq.dev>
cc: pgsql-performance@postgresql.org
Subject: Re: Surprising optimizer behavior with a subquery, a GROUP BY,
 and a range filter
In-reply-to: <b75866aa-bb54-456b-8f88-6b5bc52064ca@app.fastmail.com>
References: <b75866aa-bb54-456b-8f88-6b5bc52064ca@app.fastmail.com>
Comments: In-reply-to wotq <wotq@wotq.dev>
	message dated "Fri, 02 Jan 2026 14:26:55 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <267806.1767386789.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Jan 2026 15:46:29 -0500
Message-ID: <267807.1767386789@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/267807.1767386789%40sss.pgh.pa.us>
Precedence: bulk

wotq <wotq@wotq.dev> writes:
> The following query isn't optimized as I would expect:

I don't see this misbehavior on HEAD or v18 branch tip.  I suspect
it was fixed last week by [1] and/or [2].

			regards, tom lane

[1] https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=
=3Dad66f705f
[2] https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=
=3D559f9e90d