Thanks for the suggestion. This is what I found: - pg_locks shows only one entry for my DB (I filtered by db oid). The entry is related to the relation "pg_locks" (AccessShareLock). - pg_stat_activity shows ~30 connections (since the DB is in use, this is expected) Is there anything specific I should further look into in these tables? Regarding my last post: Did we see a problem in the logs I provided in my previous post? We have seen that there are 819294 n_live_tup in the toast-table. Do we know how much space these tuple use? Do we know how much space one tuple use? Best regards, Manuel -----Original Message----- From: Adrian Klaver <adrian.klaver@xxxxxxxxxxx> Sent: 21 June 2024 22:39 To: Shenavai, Manuel <manuel.shenavai@xxxxxxx>; Achilleas Mantzios <a.mantzios@xxxxxxxxxxxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx Subject: Re: Autovacuum, dead tuples and bloat 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@xxxxxxxxxxx
