Re: Curious about dead rows.

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: Jean-David Beyer <jeandavid8(at)verizon(dot)net>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Curious about dead rows.
Date: 2007-11-13 15:21:11
Message-ID: 20071113152111.GG11563@crankycanuck.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Please don't drop the list, as someone else may see something.

On Tue, Nov 13, 2007 at 10:06:13AM -0500, Jean-David Beyer wrote:
> OK. I turned logging from "none" to "mod" and got a gawdawful lot of stuff.

Yes.

> Then I ran it and got all the inserts. Using
> grep -i delete file
> grep -i update file
> grep -i rollback file

How about ERROR?

> 2007-11-13 08:11:20 EST DEBUG: "vl_ranks": scanned 540 of 540 pages,
> containing 67945 live rows and 554 dead rows; 3000 rows in sample, 67945
> estimated total rows

If there are dead rows, something is producing them. Either INSERT is
firing a trigger that is doing something there (you won't see an UPDATE in
that case), or else something else is causing INSERTs to fail.

A

--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alan Hodgson 2007-11-13 15:49:49 Re: dell versus hp
Previous Message Stephane Bailliez 2007-11-13 15:06:50 Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table