pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: marty@outputservices.com
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Mon, 24 Jan 2005 03:56:25 +0200
Message-ID: <1106531786.5790.9.camel@fuji.krosing.net> (raw)
In-Reply-To: <6346.1106512803@sss.pgh.pa.us>
References: <41F144FE.30902@outputservices.com>
	<41F14758.4030602@outputservices.com>
	<20050122.121300.41631131.t-ishii@sra.co.jp>
	<25335.1106428223@sss.pgh.pa.us>
	<1106511352.31592.112.camel@localhost.localdomain>
	<6346.1106512803@sss.pgh.pa.us>

Ühel kenal päeval (pühapäev, 23. jaanuar 2005, 15:40-0500), kirjutas Tom
Lane:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > Changing the idea slightly might be better: if a row update would cause
> > a block split, then if there is more than one row version then we vacuum
> > the whole block first, then re-attempt the update.
> 
> "Block split"?  I think you are confusing tables with indexes.
> 
> Chasing down prior versions of the same row is not very practical
> anyway, since there is no direct way to find them.
> 
> One possibility is, if you tried to insert a row on a given page but
> there's not room, to look through the other rows on the same page to see
> if any are deletable (xmax below the GlobalXmin event horizon).  This
> strikes me as a fairly expensive operation though, especially when you
> take into account the need to get rid of their index entries first.

Why is removing index entries essential ?

In pg yuo always have to visit data page, so finding the wrong tuple
there could just produce the same result as deleted tuple (which in this
case it actually is). The cleaning of index entries could be left to the
real vacuum.

-- 
Hannu Krosing <hannu@tm.ee>



view thread (131+ messages)  latest in thread

Message-ID: <1106531786.5790.9.camel@fuji.krosing.net>
Permalink:  ../1106531786.5790.9.camel@fuji.krosing.net/
Also on:    postgresql.org/message-id/1106531786.5790.9.camel@fuji.krosing.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: hannu@tm.ee, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, t-ishii@sra.co.jp, marty@outputservices.com, herve@elma.fr
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <1106531786.5790.9.camel@fuji.krosing.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