How can one tell if the autovacuum daemon in Postgres 9.x is running and maintaining the database cluster?

In PostgreSQL 9.5 I've decided to create a materialized view "effects" and scheduled an hourly concurrent refresh, since I wanted it to be always available: REFRESH MATERIALIZED VIEW CONCURRENTLY ...

How does one enable autovacuum in PostgreSQL? I understand the purpose, I just can't find a simple answer regarding how to enable it.

Our Postgres DB (hosted on Google Cloud SQL with 1 CPU, 3.7 GB of RAM, see below) consists mostly of one big ~90GB table with about ~60 million rows. The usage pattern consists almost exclusively o...

There is one table in my schema that does not get autovacuumed. If I run VACUUM posts; on the table the vacuum process finishes nicely, but the autovacuum daemon never vacuums the table for some re...

I wanted to utilize the power of index-only scans in Postgres and experimented with one table: CREATE TABLE dest.contexts ( id integer NOT NULL, phrase_id integer NOT NULL, lang character varyi...

Quick question from a PostgreSQL (relative) newb: We run a batch process that, as its final step, deletes most of the previous batches. Disk space is a concern, so we need to ensure that PostgreS...

I upgraded my 9.4 postgresql cluster to 9.6. (via pg_upgrade, so my db stats were not moved to a new cluster) I have a large table(about 450M records). This table is much used in my code(many selec...

I have Postgres 9.2 on my Openshift Online cartridge. Using Pgadmin3, I have enabled (by ticking the box) the autovuum setting for postgresql.conf. However, the autovacuum does not seem to be runni...

I have big tables in which I have only inserts and selects, so when autovacuum for this tables is running - system is very slow. I have switch off autovacuum for specific tables: ALTER TABLE ag_ev...

I have an autovacuum process running on pg_toast: select query, from pg_stat_activity where query like '%autov%'; "autovacuum: VACUUM pg_toast.pg_toast_15404513 " How do I find out what table/in...

I have PostgreSQL 9.2 running on Ubuntu. The autovacuum process is running on the server. The database has heavy load, 1000's of additions and 100's of deletions daily and yet it seems that auto...

There is an autovacuum query that is taking a very long time to run, and preventing alter queries to run. What is the danger is killing this autovacuum process before it's done? PID QUERY 16967 ...

in the pre-8.x days I have run numerous PGSQL databases on Linux, and did the database vacuuming explicitly via maintenance script. When 8.x came along I did not move to autovacuum on those system...