-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

PostgreSQL 10 Administration Cookbook

If you're currently waiting for a long running vacuum (or autovacuum) to finish, go straight to the How to do it... section.
If you've just had a long running vacuum then you may want to think about setting a few parameters.
autovacuum_max_workers
should always be set to more than 2. Setting it too high may not be very useful, so be careful.
Setting vacuum_cost_delay
too high is counterproductive. VACUUM
is your friend, not your enemy, so delaying it until it doesn't happen at all just makes things worse.
maintenance_work_mem
should be set to anything up to 1 GB, according to how much memory you can allocate to this task at this time.
Let's watch what happens when we run a large VACUUM.
First, locate which process is running the VACUUM
by using the pg_stat_activity
view to identify the specific pid
.
Repeatedly execute this query to see the progress of the VACUUM
command:
postgres=# SELECT * FROM pg_stat_progress_vacuum WHERE pid = 34399;