From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dan Harris <fbsd@drivefaster.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Minimizing dead tuples caused by update triggers
Date: Wed, 19 Dec 2007 19:39:45 -0500
Message-ID: <1279.1198111185@sss.pgh.pa.us> (raw)
In-Reply-To: <624895BA-B4D0-470B-80FC-4AE55C4FD85E@drivefaster.net>
References: <624895BA-B4D0-470B-80FC-4AE55C4FD85E@drivefaster.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, fbsd@drivefaster.net
Subject: Re: Minimizing dead tuples caused by update triggers
In-Reply-To: <1279.1198111185@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox