Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dvoLw-0007RS-VX for pgsql-hackers@arkaria.postgresql.org; Sat, 23 Sep 2017 17:36:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dvoLv-0001ew-Te for pgsql-hackers@arkaria.postgresql.org; Sat, 23 Sep 2017 17:36:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dvoLv-0001el-3M for pgsql-hackers@postgresql.org; Sat, 23 Sep 2017 17:36:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dvoLs-0000C8-1d for pgsql-hackers@postgresql.org; Sat, 23 Sep 2017 17:36:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v8NHaNDT015156; Sat, 23 Sep 2017 13:36:23 -0400 From: Tom Lane To: "Bossart, Nathan" cc: Michael Paquier , Alvaro Herrera , PostgreSQL mailing lists Subject: Re: Rethinking autovacuum.c memory handling In-reply-to: <9E08B120-31DE-4B47-9C44-305619F3195C@amazon.com> References: <13849.1506114543@sss.pgh.pa.us> <9E08B120-31DE-4B47-9C44-305619F3195C@amazon.com> Comments: In-reply-to "Bossart, Nathan" message dated "Sat, 23 Sep 2017 17:27:08 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15154.1506188183.1@sss.pgh.pa.us> Date: Sat, 23 Sep 2017 13:36:23 -0400 Message-ID: <15155.1506188183@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org "Bossart, Nathan" writes: > This looks reasonable to me as well. I haven't noticed any issues after > a couple hours of pgbench with aggressive autovacuum settings, either. Thanks for looking. As I'm sure you realize, what motivated that was not liking the switch into AutovacMemCxt that you'd added in autovacuum_do_vac_analyze ... with this patch, we can drop that. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers