Re: Minimizing dead tuples caused by update triggers - Mailing list pgsql-performance

From Tom Lane
Subject Re: Minimizing dead tuples caused by update triggers
Date
Msg-id 1279.1198111185@sss.pgh.pa.us
Whole thread Raw
In response to Minimizing dead tuples caused by update triggers  (Dan Harris <fbsd@drivefaster.net>)
Responses Re: Minimizing dead tuples caused by update triggers  (Decibel! <decibel@decibel.org>)
List pgsql-performance
Dan Harris <fbsd@drivefaster.net> 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

pgsql-performance by date:

Previous
From: Dan Harris
Date:
Subject: Minimizing dead tuples caused by update triggers
Next
From: Decibel!
Date:
Subject: Re: Measuring table and index bloat