pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jean-David Beyer <jeandavid8@verizon.net>
To: pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Curious about dead rows.
Date: Sat, 10 Nov 2007 21:22:58 -0500
Message-ID: <47366782.7050600@verizon.net> (raw)
In-Reply-To: <dcc563d10711101811l6bc7a521vc299f5fdbb6b7a6e@mail.gmail.com>
References: <4735DBDB.5050208@verizon.net>
	<16627.1194714491@sss.pgh.pa.us>
	<4735FA9F.1080805@verizon.net>
	<20071110105119.35346a29@scratch>
	<47360D16.7070107@verizon.net>
	<dcc563d10711101811l6bc7a521vc299f5fdbb6b7a6e@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Marlowe wrote:
> On Nov 10, 2007 1:57 PM, Jean-David Beyer <jeandavid8@verizon.net> wrote:
>> Joshua D. Drake wrote:
>>> Truncate will not create dead rows. However ROLLBACK will. Are you
>>> getting any duplicate key errors or anything like that when you insert?
>>>
>> On the mistaken assumption that TRUNCATE left dead rows, I did a
>> VACUUM FULL ANALYZE before running the program full of INSERTs. This did not
>> make any difference.
>>
>> As far as ROLLBACK are concerned, every one is immediately preceded by a
>> message output to the standard error file, and no such messages are produced.
> 
> So, there are NO failed inserts, and no updates?  Cause that's what
> I'd expect to create the dead rows.
> 
So would I. Hence the original question.

- --
  .~.  Jean-David Beyer          Registered Linux User 85642.
  /V\  PGP-Key: 9A2FC99A         Registered Machine   241939.
 /( )\ Shrewsbury, New Jersey    http://counter.li.org
 ^^-^^ 21:20:01 up 18 days, 14:38, 0 users, load average: 4.38, 4.40, 4.31
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFHNmeBPtu2XpovyZoRAqxzAJ9wLNf7Y9egSd/COtMjWaqKWfJXowCfdDj7
HEulOz8v4DKtAqWCGTf/22Y=
=79AU
-----END PGP SIGNATURE-----



view thread (41+ messages)  latest in thread

Message-ID: <47366782.7050600@verizon.net>
Permalink:  ../47366782.7050600@verizon.net/
Also on:    postgresql.org/message-id/47366782.7050600@verizon.net

 · 

reply

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: jeandavid8@verizon.net
  Subject: Re: Curious about dead rows.
  In-Reply-To: <47366782.7050600@verizon.net>

* 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