Re: postgresql meltdown on PlanetMath.org - Mailing list pgsql-performance

From Manfred Koizar
Subject Re: postgresql meltdown on PlanetMath.org
Date
Msg-id 00ih7vcuu5gf29oep2hi9sctrnui061ogh@4ax.com
Whole thread Raw
In response to Re: postgresql meltdown on PlanetMath.org  ("Kendrick C. Wilson" <kendrick_wilson@hotmail.com>)
List pgsql-performance
On Tue, 18 Mar 2003 09:19:44 -0600, "Kendrick C. Wilson"
<kendrick_wilson@hotmail.com> wrote:
>If there are multiple values, the location of the first record is found in
>the indexFile.
>
>Then dataFile is scanned until this != 'whatever';

Nice, but unfortunately not true for Postgres.  When you do the first
UPDATE after CLUSTER the new version of the changed row(s) are written
to the end of the dataFile (heap relation in Postgres speech).  So the
*index* has to be scanned until this != 'whatever'.

>Clustering is good for queries that return multiple [rows with the same search] values.

Yes.  With clustering you can expect that most of the tuples you want
are near to each other and you find several of them in the same page.

Servus
 Manfred

pgsql-performance by date:

Previous
From: Lodovico
Date:
Subject: Re: ABOUT YOUR CREDIT......... lquwj
Next
From: Torsten Schulz
Date:
Subject: Make PGSQL faster