Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UfZvV-0005vG-Nz for pgsql-performance@arkaria.postgresql.org; Thu, 23 May 2013 18:07:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UfZvV-00052O-7j for pgsql-performance@arkaria.postgresql.org; Thu, 23 May 2013 18:07:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UfZvU-00052F-Ej for pgsql-performance@postgresql.org; Thu, 23 May 2013 18:07:44 +0000 Received: from smtp.01.com ([199.36.142.181]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UfZvL-0004ae-K7 for pgsql-performance@postgresql.org; Thu, 23 May 2013 18:07:44 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id B9A502940B3; Thu, 23 May 2013 13:07:32 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpJMk-9TzGDp; Thu, 23 May 2013 13:07:32 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 9AAAE294114; Thu, 23 May 2013 13:07:32 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 8BA85294110; Thu, 23 May 2013 13:07:32 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DDdJR8CIgRHL; Thu, 23 May 2013 13:07:32 -0500 (CDT) Received: from [172.24.143.235] (unknown [137.122.64.70]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 378342940B3; Thu, 23 May 2013 13:07:30 -0500 (CDT) Message-ID: <5191B73C.9040100@agliodbs.com> Date: Mon, 13 May 2013 21:02:04 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Andres Freund CC: pgsql-performance@postgresql.org Subject: Re: Setting vacuum_freeze_min_age really low References: <5150B415.9060907@agliodbs.com> <518ED420.4090201@agliodbs.com> <20130512125027.GA7618@awork2.anarazel.de> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 1.5 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org HAndres, > Well. For one you haven't proven that the changed setting actually > improves performance. So the comparison isn't really valid. We will I agree that I haven't proven this yet, but that doesn't make it invalid. Just unproven. I agree that performance testing is necessary ... and the kind of performance testing which generated freeze activity, which makes it harder. > I think you're missing the fact that we don't neccessarily dirty pages, > just because vacuum visits them. In a mostly insert workload its not > uncommon that vacuum doesn't change anything. In many scenarios the Hmmm. But does vacuum visit the pages anyway, in that case? > b) freezing tuples requires a xlog_heap_freeze wal record to be > emitted. If we don't freeze, we don't need to emit it. Oh, that's annoying. > I think I have said that before, but anyway: I think as long as we need > to regularly walk the whole relation for correctness there isn't much > hope to get this into an acceptable state. If we would track the oldest > xid in a page in a 'freeze map' we could make much of this more > efficient and way more scalable to bigger data volumes. Yeah, or come up with some way to eliminate freezing entirely. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance