Skip site navigation (1) Skip section navigation (2)

Re: Minimizing dead tuples caused by update triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dan Harris <fbsd(at)drivefaster(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Minimizing dead tuples caused by update triggers
Date: 2007-12-20 00:39:45
Message-ID: 1279.1198111185@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Dan Harris <fbsd(at)drivefaster(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Decibel!Date: 2007-12-20 01:45:25
Subject: Re: Measuring table and index bloat
Previous:From: Dan HarrisDate: 2007-12-19 23:38:25
Subject: Minimizing dead tuples caused by update triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group