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 ) id 1vbmZj-00D09x-2q for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jan 2026 21:20:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vbmZi-00BGAf-0Q for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jan 2026 21:20:46 +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 ) id 1vbmZh-00BGAX-2f for pgsql-hackers@lists.postgresql.org; Fri, 02 Jan 2026 21:20:46 +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 ) id 1vbmZf-0048lr-2n; Fri, 02 Jan 2026 21:20:46 +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 602LKfhg271339; Fri, 2 Jan 2026 16:20:41 -0500 From: Tom Lane To: Robert Haas cc: Richard Guo , PostgreSQL Hackers Subject: Re: pgsql: Ignore PlaceHolderVars when looking up statistics In-reply-to: References: Comments: In-reply-to Robert Haas message dated "Fri, 02 Jan 2026 15:46:13 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <271337.1767388841.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 02 Jan 2026 16:20:41 -0500 Message-ID: <271338.1767388841@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Sun, Dec 28, 2025 at 9:45=E2=80=AFPM Richard Guo wrote: >> Back-patch to v18. Although this issue exists before that, changes in >> this version made it common enough to notice. Given the lack of field >> reports for older versions, I am not back-patching further. > Generally we don't back-patch fixes that could change plans, because > it tends to produce user complaints. It's maybe more justifiable in > this case because v18 is quite new and you didn't back-patch to older > releases, but are we sure that it's warranted even there? It's a regression if we don't. See nearby complaint at https://www.postgresql.org/message-id/flat/b75866aa-bb54-456b-8f88-6b5bc52= 064ca%40app.fastmail.com That case was correctly handled in v17 and before. regards, tom lane