Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZGjg-0007jE-Rc for pgsql-bugs@arkaria.postgresql.org; Sun, 01 Nov 2020 17:01:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kZGjf-0004oI-QL for pgsql-bugs@arkaria.postgresql.org; Sun, 01 Nov 2020 17:01:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZGjf-0004oB-Kl for pgsql-bugs@lists.postgresql.org; Sun, 01 Nov 2020 17:01:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZGjd-0001xP-IZ for pgsql-bugs@lists.postgresql.org; Sun, 01 Nov 2020 17:01:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0A1H1c5j387273; Sun, 1 Nov 2020 12:01:38 -0500 From: Tom Lane To: Max Vikharev cc: Jeff Janes , pgsql-bugs Subject: Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted In-reply-to: References: <16691-e029ffaaf2e1e10c@postgresql.org> Comments: In-reply-to Max Vikharev message dated "Sun, 01 Nov 2020 09:18:43 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <387271.1604250098.1@sss.pgh.pa.us> Date: Sun, 01 Nov 2020 12:01:38 -0500 Message-ID: <387272.1604250098@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Max Vikharev writes: >> finishing that table and moving to another in the same database > Yes, that case. Vacuum processes relations in one database In cycle It sounds like it's failing to advance that database's datfrozenxid and/or datminmxid. You might try to figure out which table is holding those values back by comparing pg_class.relfrozenxid and relminmxid to those pg_database columns. Then look to see if autovacuum is failing on that table, and/or try a manual vacuum to see what happens. regards, tom lane