pasman pasmański <pasman.p 'at' gmail.com> writes:
> Thanks for reply.
> I tested random changes and query runs fastest after:
> set seq_page_cost = 0.1;
> set random_page_cost = 0.1;
> cpu_operator_cost = 0.01
If I'm correct, you're basically telling postgresql that your
disk is unusually fast compared to your CPU. Even if some queries
will run faster from a side-effect of these settings, you're
likely to create other random problems...
In response to
pgsql-performance by date
|Next:||From: Marti Raudsepp||Date: 2010-12-22 10:58:33|
|Subject: Re: MySQL HandlerSocket - Is this possible in PG?|
|Previous:||From: pasman pasmański||Date: 2010-12-22 09:22:00|
|Subject: Re: Query uses incorrect index|