Re: PostgreSQL and a Catch-22 Issue related to dead rows - Mailing list pgsql-performance

From Greg Sabino Mullane
Subject Re: PostgreSQL and a Catch-22 Issue related to dead rows
Date
Msg-id CAKAnmmJLzTQAEzyBoLhG40WEN3siWFSBT68GSu2b_mF=WJL-JQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL and a Catch-22 Issue related to dead rows  (Lars Aksel Opsahl <Lars.Opsahl@nibio.no>)
Responses Re: PostgreSQL and a Catch-22 Issue related to dead rows
List pgsql-performance
On Tue, Dec 10, 2024 at 3:55 AM Lars Aksel Opsahl <Lars.Opsahl@nibio.no> wrote:
Is it difficult to add parameter like force-dead-rows-removal that we send to the vacuum job that will remove this rows like this ?
I'm still not sure what the ask here is - complete literal removal of the dead rows? That's not how PG works. I'm wondering if we are not in an XY problem. Your queries are slow, and you think it's because of autovacuum's output re dead rows. But let's take a step back and look at the actual queries being run that are slowing down. Perhaps there are other solutions: less indexing, more freezing, smarter updates, different partitioning, tweaking fillfactor, etc. etc. There are lots of things we can try that will be orders of magnitude simpler than trying to redesign MVCC/vacuuming. :) 

Cheers,
Greg

pgsql-performance by date:

Previous
From: David Mullineux
Date:
Subject: Re: can a blocked transaction affect the performance of one that is blocking it?
Next
From: Lars Aksel Opsahl
Date:
Subject: Re: PostgreSQL and a Catch-22 Issue related to dead rows