Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id DD9B12E0067 for ; Wed, 19 Dec 2007 20:39:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 89938-10 for ; Wed, 19 Dec 2007 20:39:44 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7387B2E005F for ; Wed, 19 Dec 2007 20:39:54 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBK0djkE001280; Wed, 19 Dec 2007 19:39:45 -0500 (EST) To: Dan Harris cc: pgsql-performance@postgresql.org Subject: Re: Minimizing dead tuples caused by update triggers In-reply-to: <624895BA-B4D0-470B-80FC-4AE55C4FD85E@drivefaster.net> References: <624895BA-B4D0-470B-80FC-4AE55C4FD85E@drivefaster.net> Comments: In-reply-to Dan Harris message dated "Wed, 19 Dec 2007 16:38:25 -0700" Date: Wed, 19 Dec 2007 19:39:45 -0500 Message-ID: <1279.1198111185@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/296 X-Sequence-Number: 28112 Dan Harris writes: > The thing that concerns me is dead tuples on the table_stats table. I > believe that every insert of new data in one of the monitored tables > will result in an UPDATE of the table_stats table. When thousands > ( or millions ) of rows are inserted, the select performance ( even > trying with an index ) on table_stats slows down in a hurry. Yup. FWIW, 8.3's "HOT" tuple updates might help this quite a lot. Not a lot to be done about it in 8.0.x though :-( regards, tom lane