From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: regression in PG 15.1
Date: Mon, 28 Nov 2022 07:57:16 -0700
Message-ID: <4B29C00C-028D-43AE-98F8-793BFC461CA5@elevated-dev.com> (raw)
In-Reply-To: <543106.1669646690@sss.pgh.pa.us>
References: <D86D21A2-20CB-4E28-AF0A-8C2C0139DA97@elevated-dev.com>
<543106.1669646690@sss.pgh.pa.us>
> On Nov 28, 2022, at 7:44 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Why do you say this is a regression? From what I know of the partition
> pruning logic (admittedly not a whole lot), I don't think we'd have
> ever pruned on the basis of such a constraint.
Because performance of the query tanked. If it's not a change in table pruning, then it's a change in whether/how/which indexes are used. I guess I'll have to dig into it more and get back to the list--probably tomorrow.
Meantime, thanks for the clue to help guide me here.
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-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: regression in PG 15.1
In-Reply-To: <4B29C00C-028D-43AE-98F8-793BFC461CA5@elevated-dev.com>
* 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