Re: PostgreSQL clustering VS MySQL clustering

From: Kevin Brown <kevin(at)sysexperts(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: 2005-01-28 20:46:10
Message-ID: 20050128204610.GB31166@filer
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)sysexperts(dot)com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2005-01-28 20:50:42 Re: Poor Performance on Postgres 8.0
Previous Message Dawid Kuroczko 2005-01-28 19:59:05 Re: Flattening a kind of 'dynamic' table