Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayL3F-0000xa-7I for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 15:18:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayL3E-0004m1-Qp for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 15:18:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ayL1Y-0002uJ-6s for pgsql-admin@postgresql.org; Thu, 05 May 2016 15:17:08 +0000 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ayL1V-0006kj-0I for pgsql-admin@postgresql.org; Thu, 05 May 2016 15:17:07 +0000 Received: by mail-wm0-x235.google.com with SMTP id n129so24684914wmn.1 for ; Thu, 05 May 2016 08:17:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flexibee-eu.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=2vesxVRwLkssu1ZRsxWQyIYG5a4kU/lLmRsclJGOuUo=; b=FU1ri3Vf/fn+Vlbn1+sxFx72sjxhwHboHqp5CSFvHtZXl+PGvGYyAsKteQc45coZnO iO5z1/TSR6n+ewfs97QoiQJcE/293iTJVZu6ThvwU8GwFlbFw5HR4pYB2dpRFQj3sxD/ Cs5bRUS44mzo7dm1NkyWt0Bh8mj6XSjfThNE7F/noX2TbpCWdauVKSRvHCgnN0vrUW1H ihLv/ZPFXy6nEkyi/3xEo97eN+JEk+O4hlaOtkHSwXx/wcDElb5iKRxtgoUQhDbY5F3Z RTGQrZyjZWp0A+/AQkqUdYwFdX8nECFy/I7HxcZXReyfmaVsOcbJHRXh9ERRpJZ2JX/y JgIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=2vesxVRwLkssu1ZRsxWQyIYG5a4kU/lLmRsclJGOuUo=; b=DBQkPq0KW3G8RNUNrY/+/ZsUXg5uHE4ulzrrRTg0MdaYkffGZ5tN6a8fMY8RYd+Bgg ht8YiIAQZEWIC1OvI8f6RPXjK1DHoKhvsy395IM1FelBmxvK4aMvVSm63fqCzphgrur+ Db2y7kU27lMw+tpUviEvYz/HrX4jkFuH8XZXYebiZSK0u7oox1L8R5XRuAZPNTWgEM3K 06QetgIZm8dLxB2OZt7C+4ZypA69uGfm6rPblU0/XlryfySrwjFQNXB1OVEf1EcJG/p1 hJQh6t5Ih7cxsfghWNxn++7wxYRVcB2iLNKjNHzeCt0qAbYoImAwadieY8SdxjBEFo8n 0hmg== X-Gm-Message-State: AOPr4FXYgxKY2ZSmI3cQKoUlTwW1SOUs0OXxbkxe9hTuG3nH7QeJ9BJFXCoJsXta4IUB/cJm X-Received: by 10.28.0.78 with SMTP id 75mr3873130wma.20.1462461362991; Thu, 05 May 2016 08:16:02 -0700 (PDT) Received: from osvetlik-nb.localdomain ([88.208.120.47]) by smtp.gmail.com with ESMTPSA id j6sm10193838wjb.29.2016.05.05.08.16.01 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 May 2016 08:16:02 -0700 (PDT) To: pgsql-admin@postgresql.org From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= Subject: Autovacuum of pg_database Message-ID: <572B63B1.3030603@flexibee.eu> Date: Thu, 5 May 2016 17:16:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hello again, we have another strange problem with autovacuum. The process goes well until it reaches the table pg_database (in some databases, not all), then it loops over it forever (until I run vacuum full analyze on that table, simple vacuum doesn't help): 2016-05-05 17:13:33 CEST 34818LOG: automatic vacuum of table "somedatabase.pg_catalog.pg_database": index scans: 0 pages: 0 removed, 233 remain tuples: 0 removed, 5817 remain, 0 are dead but not yet removable buffer usage: 87 hits, 0 misses, 0 dirtied avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec 2016-05-05 17:13:33 CEST 34819LOG: automatic vacuum of table "somedatabase.pg_catalog.pg_database": index scans: 0 pages: 0 removed, 233 remain tuples: 0 removed, 5817 remain, 0 are dead but not yet removable buffer usage: 87 hits, 0 misses, 0 dirtied avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec 2016-05-05 17:13:33 CEST 34820LOG: automatic vacuum of table "somedatabase.pg_catalog.pg_database": index scans: 0 pages: 0 removed, 233 remain tuples: 0 removed, 5817 remain, 0 are dead but not yet removable buffer usage: 87 hits, 0 misses, 0 dirtied avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec 2016-05-05 17:13:34 CEST 34821LOG: automatic vacuum of table "somedatabase.pg_catalog.pg_database": index scans: 0 pages: 0 removed, 233 remain tuples: 0 removed, 5817 remain, 0 are dead but not yet removable buffer usage: 87 hits, 0 misses, 0 dirtied avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec Not sure if it's a bug or I'm doing something wrong. Thanks in advance, Ondřej -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin