Jeroen van Iddekinge wrote:


You could tweak with several settings to get it to do an index scan earlier, but these would probably break other queries. You don't need to tune for 100 rows, morelike 100k or 100M.


Thanks for respone.
The index scan was a little bit faster for id=1 and faster for id=99.

Which settings shoud I change for this?  cpu_index_tuple_cost ,
cpu_operator_cost, cpu_tuple_cost?


Jer.

Well, I would start with *don't*. You are only looking at one query, which is pretty much fast already, and probably is not going to be the bottleneck. You are optimizing the wrong thing.

That being said, because you have everything cached in ram (since it is
a tiny table), you probably would set random_page_cost = 2.

In theory it should really never be lower than 2, though if you are
trying to force an index scan you can do it.

John
=:->


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to