pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Brown <kevin@sysexperts.com>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Fri, 28 Jan 2005 12:46:10 -0800
Message-ID: <20050128204610.GB31166@filer> (raw)
In-Reply-To: <opsk76kbw7th1vuj@musicbox>
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>
	<20050125031104.GW67721@decibel.org>
	<opsk76kbw7th1vuj@musicbox>

PFC wrote:
> So, here is something annoying with the current approach : Updating rows  
> in a table bloats ALL indices, not just those whose indexed values have  
> been actually updated. So if you have a table with many indexed fields and  
> you often update some obscure timestamp field, all the indices will bloat,  
> which will of course be corrected by VACUUM, but vacuum will have extra  
> work to do.

The MVCC approach probably doesn't leave you with many choices here.
The index entries point directly to the rows in the table, and since
an update creates a new row (it's the equivalent of doing an insert
then a delete), all indexes have to be updated to reflect the location
of the new row.

Unless my understanding of how this works is completely off...




-- 
Kevin Brown					      kevin@sysexperts.com



view thread (131+ messages)  latest in thread

Message-ID: <20050128204610.GB31166@filer>
Permalink:  ../20050128204610.GB31166@filer/
Also on:    postgresql.org/message-id/20050128204610.GB31166@filer

 · 

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: kevin@sysexperts.com
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <20050128204610.GB31166@filer>

* 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