Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 02A552E15CD for ; Tue, 13 Nov 2007 17:35:21 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 98506-06 for ; Tue, 13 Nov 2007 17:35:14 -0400 (AST) Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id 0B76C2E1275 for ; Tue, 13 Nov 2007 17:35:17 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1Is3Pg-0000uN-05 for pgsql-performance@postgresql.org; Tue, 13 Nov 2007 16:35:16 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id BA931504FB; Tue, 13 Nov 2007 16:35:10 -0500 (EST) Date: Tue, 13 Nov 2007 16:35:10 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: Curious about dead rows. Message-ID: <20071113213510.GF11563@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-performance@postgresql.org References: <20071112163223.GP32349@crankycanuck.ca> <4738825F.6050106@verizon.net> <20071112171805.GQ32349@crankycanuck.ca> <47389504.4020700@verizon.net> <20071112185218.GS32349@crankycanuck.ca> <4738A2EC.9090500@verizon.net> <20071112190833.GY32349@crankycanuck.ca> <4739BD65.9070605@verizon.net> <20071113152111.GG11563@crankycanuck.ca> <473A0023.5020609@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <473A0023.5020609@verizon.net> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/199 X-Sequence-Number: 27614 On Tue, Nov 13, 2007 at 02:50:59PM -0500, Jean-David Beyer wrote: > > How about ERROR? > > $ grep -i error Tue.log > $ Well, without actually logging into the machine and looking at the application, I confess I am stumped. Oh, wait. You do have the log level high enough that you should see errors in the log, right? That's not controlled by the statement parameter. > I have no triggers in that database. I do have two sequences. Sequences should not produce any dead rows on the table, unless they're used as keys and you're attempting inserts that conflict with used sequence values. That should cause errors that you'd get in the log, presuming that you have the log level set correctly. A -- Andrew Sullivan Old sigs will return after re-constitution of blue smoke