Re: Autovacuum, dead tuples and bloat
От | Adrian Klaver |
---|---|
Тема | Re: Autovacuum, dead tuples and bloat |
Дата | |
Msg-id | 53da5a20-ca35-40fa-85a3-c59d4302a512@aklaver.com обсуждение исходный текст |
Ответ на | RE: Autovacuum, dead tuples and bloat ("Shenavai, Manuel" <manuel.shenavai@sap.com>) |
Ответы |
RE: Autovacuum, dead tuples and bloat
|
Список | pgsql-general |
On 6/21/24 12:31, Shenavai, Manuel wrote: > Hi, > > Thanks for the suggestions. I found the following details to our > autovacuum (see below). The related toast-table of my table shows some > logs related the vacuum. This toast seems to consume all the data > (27544451 pages * 8kb ≈ 210GB ) Those tuples(pages) are still live per the pg_stat entry in your second post: "n_dead_tup": 12, "n_live_tup": 819294 So they are needed. Now the question is why are they needed? 1) All transactions that touch that table are done and that is the data that is left. 2) There are open transactions that still need to 'see' that data and autovacuum cannot remove them yet. Take a look at: pg_stat_activity: https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW and pg_locks https://www.postgresql.org/docs/current/view-pg-locks.html to see if there is a process holding that data open. > > Any thoughts on this? > > Best regards, > Manuel > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: