Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id DC6352E2CC4 for ; Wed, 14 Nov 2007 17:34:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 30684-05 for ; Wed, 14 Nov 2007 17:34:33 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 9BEF52E2368 for ; Wed, 14 Nov 2007 17:34:41 -0400 (AST) Received: from perhan.alvh.no-ip.org (190-95-16-8.bk17-dsl.surnet.cl [190.95.16.8]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id lAELYbPc027196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Nov 2007 13:34:40 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 647A147C0D; Wed, 14 Nov 2007 18:35:04 -0300 (CLST) Date: Wed, 14 Nov 2007 18:35:04 -0300 From: Alvaro Herrera To: Jean-David Beyer Cc: pgsql performance Subject: Re: Curious about dead rows. Message-ID: <20071114213504.GW19014@alvh.no-ip.org> References: <4735DBDB.5050208@verizon.net> <473B4AB4.70506@sime.com> <473B6398.9030507@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <473B6398.9030507@verizon.net> User-Agent: Mutt/1.5.16 (2007-06-11) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 14 Nov 2007 13:34:40 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/220 X-Sequence-Number: 27635 Jean-David Beyer wrote: > Mario Weilguni wrote: > > Did you rollback some transactions? It will generate dead rows too - at > > least I think so. > > > No, and the statistics confirm this. To recap: - your app only does inserts - there has been no rollback lately - there are no updates - there are no deletes The only other source of dead rows I can think is triggers ... do you have any? (Not necessarily on this table -- perhaps triggers on other tables can cause updates on this one). Oh, rolled back COPY can cause dead rows too. -- Alvaro Herrera http://www.PlanetPostgreSQL.org/ "Before you were born your parents weren't as boring as they are now. They got that way paying your bills, cleaning up your room and listening to you tell them how idealistic you are." -- Charles J. Sykes' advice to teenagers