Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g4Xtb-0005hB-PW for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Sep 2018 20:55:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g4XtY-0006Qn-MS for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Sep 2018 20:55: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.89) (envelope-from ) id 1g4XtY-0006Qa-8X for pgsql-hackers@lists.postgresql.org; Mon, 24 Sep 2018 20:55:52 +0000 Received: from forward4o.cmail.yandex.net ([2a02:6b8:0:1a72::289]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g4XtU-0005Xa-0q for pgsql-hackers@lists.postgresql.org; Mon, 24 Sep 2018 20:55:51 +0000 Received: from mxback19j.mail.yandex.net (mxback19j.mail.yandex.net [IPv6:2a02:6b8:0:1619::95]) by forward4o.cmail.yandex.net (Yandex) with ESMTP id C603320BDF; Mon, 24 Sep 2018 23:55:42 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback19j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id zOhjqaO1zI-tfV0Kbiu; Mon, 24 Sep 2018 23:55:41 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail; t=1537822541; bh=tJZ4awoJzaAyJ2JMMj0wU+T7GE2LpnZo3vsFvqKE4w8=; h=From:To:Cc:In-Reply-To:References:Subject:Date:Message-Id; b=m8DB4AZX5Mdv4CE1WdZdYoOKIPV4IQYQEK6rCAYjJf3echzzHNTqwfYRWOl/eDZCd Qa78AFIThCqgWUKkx9to/3/3KKXO2rxpFFMfhWt5H6uQtpsrkL5CKSQESIlBBFZhV+ 0INrIlef9edHjiFCQaP8Sw1dSrrGtwzPKqJgaEEA= Authentication-Results: mxback19j.mail.yandex.net; dkim=pass header.i=@zsrv.org Received: by iva4-6d7004ac8463.qloud-c.yandex.net with HTTP; Mon, 24 Sep 2018 23:55:41 +0300 From: Sergei Kornilov To: "Nasby, Jim" , Andres Freund Cc: Robert Haas , Alvaro Herrera , Michael Paquier , PostgreSQL Hackers In-Reply-To: <0A11E30F-DDDE-422F-B22A-3F6E3AA7A0A2@amazon.com> References: <20180914153554.562muwr3uwujno75@alvherre.pgsql> <7924791537551496@myt5-c56023d17c6b.qloud-c.yandex.net> <20180921174347.wvszsn7uk56zvz7o@alap3.anarazel.de> <0A11E30F-DDDE-422F-B22A-3F6E3AA7A0A2@amazon.com> Subject: Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 24 Sep 2018 23:55:41 +0300 Message-Id: <23209391537822541@iva4-6d7004ac8463.qloud-c.yandex.net> Content-Transfer-Encoding: 7bit Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi > An autovacuum can't be just aggressive; it's either anti-wraparound or normal. But autovacuum _can_ be aggressive and not anti-wraparound. I build current master and can see 3 different line types: 2018-09-24 23:47:31.500 MSK 27939 @ from [vxid:4/272032 txid:0] [] LOG: automatic aggressive vacuum of table "postgres.public.foo": index scans: 0 2018-09-24 23:49:27.892 MSK 28333 @ from [vxid:4/284297 txid:0] [] LOG: automatic aggressive vacuum to prevent wraparound of table "postgres.public.foo": index scans: 0 2018-09-24 23:49:29.093 MSK 28337 @ from [vxid:4/284412 txid:0] [] LOG: automatic vacuum of table "postgres.public.foo": index scans: 0 regards, Sergei