Re: PostgreSQL index usage discussion.

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Luis Alberto Amigo Navarro <lamigo(at)atc(dot)unican(dot)es>
Cc: mlw <markw(at)mohawksoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL index usage discussion.
Date: 2002-04-25 07:48:26
Message-ID: 1019720906.6205.32.camel@taru.tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2002-04-25 at 08:42, Luis Alberto Amigo Navarro wrote:
> >
> > (2) Use programmatic hints which allow coders specify which indexes are
> used
> > during a query. (ala Oracle)
> >
> As I said before it would be useful a way to improve(not force) using
> indexes on particular queries, i.e. lowering the cost of using this index on
> this query.
> Regards

I was told that DB2 has per-table (or rather per-tablespace) knowledge
of disk speeds, so keeping separate random and seqsqan costs for each
table and index could be a good way here (to force use of a particular
index make its use cheap)

------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Curt Sampson 2002-04-25 07:55:50 Re: Sequential Scan Read-Ahead
Previous Message Francois Suter 2002-04-25 07:47:49 pid gets overwritten in OSX