Re: Postgres: Queries are too slow after upgrading to PG17 from PG15

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Todd Cook <cookt(at)blackduck(dot)com>
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date: 2025-08-05 14:47:22
Message-ID: CAH2-WznrkQYZtq2XEBSvmWzJwj6O61JaxY+eVL00FeSz7bv2vA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Aug 5, 2025 at 1:31 AM Sajith Prabhakar Shetty
<ssajith(at)blackduck(dot)com> wrote:
> Before proceeding with testing the patch against the original problematic query, I wanted to check with you — should I go ahead and apply the current patch, or would it be better to wait for any revised version based on Tom’s feedback?

I doubt that Tom's feedback will affect the performance profile of the
patch. v1 is very likely to be representative of the final patch in
every way that your testing will consider, so I see no reason to wait.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Davis 2025-08-05 16:28:24 Re: CREATE DATABASE copies datlocale even if datlocprovider differs
Previous Message Álvaro Herrera 2025-08-05 14:40:07 Re: BUG #19008: Problems downloading metadata for dnf - probably missing private key (GPG signature)