From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Jean-David Beyer <jeandavid8@verizon.net>
Cc: pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Curious about dead rows.
Date: Wed, 14 Nov 2007 18:35:04 -0300
Message-ID: <20071114213504.GW19014@alvh.no-ip.org> (raw)
In-Reply-To: <473B6398.9030507@verizon.net>
References: <4735DBDB.5050208@verizon.net>
<473B4AB4.70506@sime.com>
<473B6398.9030507@verizon.net>
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
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: alvherre@alvh.no-ip.org, jeandavid8@verizon.net
Subject: Re: Curious about dead rows.
In-Reply-To: <20071114213504.GW19014@alvh.no-ip.org>
* 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