Re: Deceiding which index to use

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mezei Zoltán wrote:
Richard Huxton wrote:

There is a cost to increasing the stats values, otherwise it'd
already be set at 1000. In your case I'm not sure if 100-200 vs 8-9
messages is enough to skew things. Only one way to find out...

Well, I tried. The situation is:

- when I look for a subscriber which the planner thinks to have more
messages --> it uses the index on crd - when I look for a subscriber
which the planner thinks to have less messages --> it uses the index
on subscriber_id

I think that's OK, even if it still don't do what I really would like
to see it do :-)

Well, it's decision about where the costs cross over will be in the other "cost" settings in postgresql.conf. The thing is, it's not worth tuning for just this one query, because you can easily end up running everything else more slowly.

Thanks for all your help, maybe I know a little bit more about
poostgresql than before.


--
  Richard Huxton
  Archonet Ltd


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux