pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Haowu Ge <gehaowu@bitmoe.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Date: Sun, 28 Dec 2025 11:51:03 -0500
Message-ID: <2509473.1766940663@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMbWs49h5F66KZwLxaeXoLwHe_9jAB7Eu44UmJhhQpLA38tKhw@mail.gmail.com>
References: <62af586c-c270-44f3-9c5e-02c81d537e3d.gehaowu@bitmoe.com>
	<CAMbWs48=zSwZEbqX4-A1jtJqWuPxu8xbkQbu+CdtHg5anM9RVg@mail.gmail.com>
	<CAMbWs48J51_SJ5nyA5P=d0mtkwvXf3rS=nOC7HL5+hjrbPZuSw@mail.gmail.com>
	<bc40b611-960b-4a98-a0ea-becd72d558d9.gehaowu@bitmoe.com>
	<CAMbWs49fQuPPMTmFL3NrshGBYoTQL26tWtg-3pA2jkmW=C5GQg@mail.gmail.com>
	<CAMbWs4-jteRUuZ63p3yyHG6=ggV9a3cNj_vMuYBrURhyXdMg_w@mail.gmail.com>
	<7543464e-d2c6-4778-add0-31a6d60e58ce.gehaowu@bitmoe.com>
	<CAMbWs48j6BvDq9aCOM_gjgM6katSyrzpdgwoBBK1F7uD8pds4w@mail.gmail.com>
	<eef00885-2b2a-4af2-b0b1-3ba04e93efe5.gehaowu@bitmoe.com>
	<CAMbWs4-99AsnnvfTuGj9C_QHXB9aNhjNyhfxXEcOWeAeq=Og5A@mail.gmail.com>
	<9e659ce0-da20-42ed-ada2-5f585a89677e.gehaowu@bitmoe.com>
	<CAMbWs4-WSvpyB=vUNjj9it+_9Qs14=cj68Vj+zQug9XR77UTQw@mail.gmail.com>
	<CAMbWs4911OFJSybB73rkxfV5L7H+XB1YG-vnAhN1wdQE=4-jYQ@mail.gmail.com>
	<0f894411-0d2c-4455-8403-f342642e49bc@bitmoe.com>
	<CAMbWs49h5F66KZwLxaeXoLwHe_9jAB7Eu44UmJhhQpLA38tKhw@mail.gmail.com>

Richard Guo <guofenglinux@gmail.com> writes:
> I've been back and forth on whether to back-patch these two patches to
> v18, given that they can lead to plan changes.

Yeah, typically we lean to not back-patching planning changes,
for fear of de-optimizing queries that may have been tuned to the
old behavior.

However, in this case there is a mitigating factor: from the users'
point of view v18's behavior is a regression.  Affected queries that
relied on indexes were fine in prior versions but now they fail to
use the indexes.  v18 is new enough that it seems unlikely that any
applications have been tuned for its behavior; we should worry more
about de-optimizing applications that haven't yet been brought
forward.

So here, I think the don't-break-things rule points towards
back-patching.

			regards, tom lane





view thread (16+ messages)  latest in thread

Message-ID: <2509473.1766940663@sss.pgh.pa.us>
Permalink:  ../2509473.1766940663@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2509473.1766940663@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, guofenglinux@gmail.com, gehaowu@bitmoe.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  In-Reply-To: <2509473.1766940663@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox