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

From Lars Aksel Opsahl
Subject Re: PostgreSQL and a Catch-22 Issue related to dead rows
Date
Msg-id AM7P189MB1028BA1F3FFE08B1517F85CD9D3C2@AM7P189MB1028.EURP189.PROD.OUTLOOK.COM
Whole thread Raw
In response to PostgreSQL and a Catch-22 Issue related to dead rows  (Lars Aksel Opsahl <Lars.Opsahl@nibio.no>)
List pgsql-performance


From: MichaelDBA@sqlexec.com <michaeldba@sqlexec.com>
Sent: Monday, December 9, 2024 2:18 PM
To: Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: PostgreSQL and a Catch-22 Issue related to dead rows
 
You could always turn off vacuuming at the table level and then resume later
Sent from my iPhone

Hi

I am running without auto vacuuming for those  tables already. 

From the application I trigger analyze and vacuum at certain conditions , but that is not solving the problem related to dead rows.

Thanks.

Lars



pgsql-performance by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: PostgreSQL and a Catch-22 Issue related to dead rows
Next
From: Lars Aksel Opsahl
Date:
Subject: Re: PostgreSQL and a Catch-22 Issue related to dead rows