| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | autovacuum is running but pg_stat_all_tables empty |
| Date: | 2018-11-19 17:31:35 |
| Message-ID: | CA+t6e1=uC1WfSpuMYwZwYhn28aQEoiAc4D9DY-VQ9ZJcBm26Uw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
Hi,
I'm trying to understand something that is weird on one of my environments.
When I query pg_stat_all_tables I see that most of the tables dont have any
value in the last_autovacuum/analyze column. In addition the columns
autovacuum_count/analyze_count is set to 0. However, when checking the
logs, I see that on some of those tables autovacuum run. I think that there
is something wrong with the database statistics collector. In addition, the
column n_dead_tup and n_live_tup are set and in some of the cases
n_dead_tup is more then 20% of the table tuples. In addition, all tables
have default vacuum threshold.
Any idea what else I can check ?
The problem isnt only that dead tuples arent deleted (I dont have long
running transaction that might cause it) but the fact that the statistics
arent accurate/wrong.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2018-11-19 18:52:43 | Re: autovacuum is running but pg_stat_all_tables empty |
| Previous Message | David G. Johnston | 2018-11-19 16:13:18 | Re: logging aql queries only one table or tables of one scheme |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2018-11-19 18:52:43 | Re: autovacuum is running but pg_stat_all_tables empty |
| Previous Message | Stephen Frost | 2018-11-19 17:26:09 | Re: PostgreSQL VS MongoDB: a use case comparison |