Re: PostgreSQL clustering VS MySQL clustering

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, marty(at)outputservices(dot)com, herve(at)elma(dot)fr, pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: 2005-01-26 15:17:43
Message-ID: 14870.1106752663@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hannu Krosing <hannu(at)tm(dot)ee> writes:
> But can't clearing up the index be left for "later" ?

Based on what? Are you going to store the information about what has to
be cleaned up somewhere else, and if so where?

> Indexscan has to check the data tuple anyway, at least for visibility.
> would adding the check for field sameness in index and data tuples be
> too big performance hit ?

It does pretty much suck, especially when you think about functional
indexes on expensive functions.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Van Ingen, Lane 2005-01-26 16:44:45 SQL Performance Guidelines
Previous Message Peter Darley 2005-01-26 15:16:25 Re: Possibly slow query