From: Craig James <craig_james@emolecules.com>
To: pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Curious about dead rows.
Date: Wed, 14 Nov 2007 19:02:49 -0800
Message-ID: <473BB6D9.6090908@emolecules.com> (raw)
In-Reply-To: <20071114213504.GW19014@alvh.no-ip.org>
References: <4735DBDB.5050208@verizon.net>
<473B4AB4.70506@sime.com>
<473B6398.9030507@verizon.net>
<20071114213504.GW19014@alvh.no-ip.org>
Alvaro Herrera wrote:
> 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.
What about an unreliable network that causes lot of disconnects? Wouldn't the server process do a rollback?
Craig
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: craig_james@emolecules.com
Subject: Re: Curious about dead rows.
In-Reply-To: <473BB6D9.6090908@emolecules.com>
* 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