Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 5604B1337B39 for ; Tue, 25 Jan 2011 17:29:45 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 09115-09 for ; Tue, 25 Jan 2011 21:29:38 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.catalyst.net.nz (bertrand.catalyst.net.nz [202.78.240.40]) by mail.postgresql.org (Postfix) with ESMTP id 1D651133798E for ; Tue, 25 Jan 2011 17:29:38 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id A2C2D321BD; Wed, 26 Jan 2011 10:29:34 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz Received: from mail.catalyst.net.nz ([127.0.0.1]) by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5Ma2YM48Xyl; Wed, 26 Jan 2011 10:29:34 +1300 (NZDT) Received: from [IPv6:2404:130:0:1000:222:15ff:fe5c:2471] (unknown [IPv6:2404:130:0:1000:222:15ff:fe5c:2471]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id 1AFEF32002; Wed, 26 Jan 2011 10:29:34 +1300 (NZDT) Message-ID: <4D3F40BD.4040504@catalyst.net.nz> Date: Wed, 26 Jan 2011 10:29:33 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Josh Berkus CC: Robert Haas , pgsql-performance@postgresql.org Subject: Re: Bloat issue on 8.3; autovac ignores HOT page splits? References: <4D3E34C8.9040209@agliodbs.com> <4D3F163E.100@agliodbs.com> In-Reply-To: <4D3F163E.100@agliodbs.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201101/234 X-Sequence-Number: 42021 On 26/01/11 07:28, Josh Berkus wrote: > > One question: in 8.3 and earlier, is the FSM used to track dead_rows for > pg_stat_user_tables? > If I'm understanding you correctly, ANALYZE is the main guy tracking/updating the dead row count. regards Mark