From: | Lars Aksel Opsahl <Lars(dot)Opsahl(at)nibio(dot)no> |
---|---|
To: | "MichaelDBA(at)sqlexec(dot)com" <michaeldba(at)sqlexec(dot)com> |
Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL and a Catch-22 Issue related to dead rows |
Date: | 2024-12-09 13:37:33 |
Message-ID: | AM7P189MB1028BA1F3FFE08B1517F85CD9D3C2@AM7P189MB1028.EURP189.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
________________________________
From: MichaelDBA(at)sqlexec(dot)com <michaeldba(at)sqlexec(dot)com>
Sent: Monday, December 9, 2024 2:18 PM
To: Lars Aksel Opsahl <Lars(dot)Opsahl(at)nibio(dot)no>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org <pgsql-performance(at)lists(dot)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Lars Aksel Opsahl | 2024-12-09 13:56:54 | Re: PostgreSQL and a Catch-22 Issue related to dead rows |
Previous Message | Greg Sabino Mullane | 2024-12-09 13:35:20 | Re: PostgreSQL and a Catch-22 Issue related to dead rows |