From: | Bradley McLean <brad(at)bradm(dot)net> |
---|---|
To: | mlw <markw(at)mohawksoft(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL index usage discussion. |
Date: | 2002-04-25 01:37:48 |
Message-ID: | 20020424213748.A11681@nia.bradm.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* mlw (markw(at)mohawksoft(dot)com) [020424 18:51]:
>
> (2) Use programmatic hints which allow coders specify which indexes are used
> during a query. (ala Oracle)
We would certainly use this if it were available. Hopefully not to
shoot ourselves in the foot, but for the rather common case of having
a small set of important predefined queries that run over data sets
that neither grow significantly nor change in characteristics (for
example, a table of airline routes and fares, with a few million
rows).
We want to squeeze every last bit of performance out of certain
queries, and we're willing to spend the time to verify that the
manual tuning beats the planner.
> What do you all think? What would be a good plan of attack?
I dunno. If someone comes up with one that I can reasonably
contribute to, I will.
-Brad
From | Date | Subject | |
---|---|---|---|
Next Message | Curt Sampson | 2002-04-25 01:40:37 | Re: Sequential Scan Read-Ahead |
Previous Message | Bruce Momjian | 2002-04-25 01:29:47 | Re: Vote totals for SET in aborted transaction |