From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sajith Prabhakar Shetty <ssajith@blackduck.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date: Fri, 16 May 2025 08:51:43 -0400
Message-ID: <16974.1747399903@sss.pgh.pa.us> (raw)
In-Reply-To: <DM4SPRMB00127B778BCB2A2032AFF420B590A@DM4SPRMB0012.namprd19.prod.outlook.com>
References: <PH7PR19MB6481278D3A55C8BD04B9B9EDB590A@PH7PR19MB6481.namprd19.prod.outlook.com>
<11970.1747323991@sss.pgh.pa.us>
<DM4SPRMB00127B778BCB2A2032AFF420B590A@DM4SPRMB0012.namprd19.prod.outlook.com>
Sajith Prabhakar Shetty <ssajith@blackduck.com> writes:
> In my first test, I used pg_upgrade to upgrade the instance from 15 to 17, and in my second test, I created PG15 and PG17 separately from brew repo, I don’t think I am using debug build here.
Might be worth checking the brew recipes... it's common for packagers to
set the debug option for beta versions, and I could believe that whoever
packages PG for HomeBrew forgot to take that out again for 17.0.
But, assuming it's not that, could you put together a self-contained
test case that demos what you're seeing?
regards, tom lane
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, ssajith@blackduck.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
In-Reply-To: <16974.1747399903@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