From: | Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> |
---|---|
To: | dave(at)fastcrypt(dot)com |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: query tuning |
Date: | 2003-08-15 15:26:12 |
Message-ID: | 1060961172.975.8.camel@taz.oficina |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I usually reduce cpu_index_tuple_cost in postgresql.conf, from 0.001 to
0.000001, this way the optimizer is "more willing" to use indexes.
Of course you should try different values until you find the ones that
adjust to your system configuration.
On Thu, 2003-08-14 at 09:00, Dave Cramer wrote:
> I have a query which definitely runs faster when sequential scans are
> turned off. Which parameters do I tune? and which way?
>
> After quickly perusing the docs, and google, I think it is the
> random_page_cost?
>
> Any help would be appreciated.
>
> Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Gearon | 2003-08-15 15:32:03 | Re: Why the duplicate messages to pgsql-general? |
Previous Message | expect | 2003-08-15 15:21:28 | Re: Why the duplicate messages to pgsql-general? |