Request a Demo
Home   >   mailing lists

Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date
Msg-id CAH2-WzmACH8cXhGG7gXj_S=nAAKMezrT7=9bUDyRoOo2sRA-4g@mail.gmail.com
Whole thread Raw
In response to Re: Postgres: Queries are too slow after upgrading to PG17 from PG15  (Sajith Prabhakar Shetty <ssajith@blackduck.com>)
Responses Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
List pgsql-bugs
Tree view 
On Tue, Aug 12, 2025 at 12:46 AM Sajith Prabhakar Shetty
<ssajith@blackduck.com> wrote:
> I can confirm with full certainty that both VACUUM and ANALYZE were executed on all three instances whose results I
shared.

The results that you shared showed "Heap Fetches: 598,916" -- one heap
fetch per index search (for the problematic index scan).

Perhaps VACUUM ran without being truly effective, due to the removable
cutoff/horizon being held back by a long running query. Though that
generally won't happen on a quiescent system -- so it really does look
like VACUUM hasn't been run.


--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
Next
From: Fujii Masao
Date:
Subject: Re: Unexpected Standby Shutdown on sync_replication_slots change