In this particular case autovacuum_count is 0. n_live_tup is 659,631 and n_dead_tup is 3,400,347.
We are using the default vacuum parameters. From: Michael Lewis [mailto:mle...@entrata.com] Sent: Thursday, December 05, 2019 5:49 PM To: Mike Schanne Cc: pgsql-performa...@postgresql.org Subject: Re: autovacuum locking question On Thu, Dec 5, 2019 at 3:26 PM Mike Schanne <mscha...@kns.com<mailto:mscha...@kns.com>> wrote: I am concerned that if the autovacuum is constantly canceled, then the table never gets cleaned and its performance will continue to degrade over time. Is it expected for the vacuum to be canceled by an insert in this way? We are using postgres 9.6.10. Have you checked when the table was last autovacuumed in pg_stat_user_tables? If the autovacuum count is high and timestamp of last run is relatively current, then no reason for concern as far as I can figure. Have you already configured (non-default values) for autovacuum options for your system or this table? ________________________________ This email is non-binding, is subject to contract, and neither Kulicke and Soffa Industries, Inc. nor its subsidiaries (each and collectively “K&S”) shall have any obligation to you to consummate the transactions herein or to enter into any agreement, other than in accordance with the terms and conditions of a definitive agreement if and when negotiated, finalized and executed between the parties. This email and all its contents are protected by International and United States copyright laws. Any reproduction or use of all or any part of this email without the express written consent of K&S is prohibited.
