Re: Further open item (Was: Status of 7.2)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Tille, Andreas" <TilleA(at)rki(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Further open item (Was: Status of 7.2)
Date: 2001-11-19 20:07:22
Message-ID: 200111192007.fAJK7MA16921@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > There is not much point in arguing a specific query case,
> It is no specific query case. It is the speed of an index scan which
> goes like N if you do it with PostgreSQL and it goes like log N if
> you do not have to look back into the table like MS SQL server does.

Have you tried using CLUSTER to match the heap order with the index
order. That should help with index scans looking up heap rows.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-11-19 20:40:35 Re: OCTET_LENGTH is wrong
Previous Message Bruce Momjian 2001-11-19 20:01:59 New TODO item