Re: Ineffective autovacuum
| От | Royce Ausburn |
|---|---|
| Тема | Re: Ineffective autovacuum |
| Дата | |
| Msg-id | A0DE3560-2C7F-4220-BED5-CC8D6266499B@inomial.com обсуждение исходный текст |
| Ответ на | Re: Ineffective autovacuum (Marti Raudsepp <marti@juffo.org>) |
| Список | pgsql-performance |
On 27/09/2011, at 8:29 PM, Marti Raudsepp wrote:
1. First things first: vacuum cannot delete tuples that are still
visible to any old running transactions. You might have some very long
queries or transactions that prevent it from cleaning properly:
select * from pg_stat_activity where xact_start < now()-interval '10 minutes';
Thanks -- that query is very handy. I suspect this might be the cause of our woes as this query results in a handful of long lived connections, however they're connections to databases other than the one that I'm having trouble with.
I've checked up on the FSM as you suggested, I don't think that's the problem as there're no warnings in the verbose output nor the logs. But another clue:
DETAIL: 93 dead row versions cannot be removed yet.
After clearing those stuffed transactions vacuum verbose manages to clear away all the dead rows… That's confirmation enough for me - Now to find the application bugs - Thanks Tom, Marti & Scott for your help!
--Royce
В списке pgsql-performance по дате отправления: