Richard Huxton wrote:
Re: [PERFORM] Deceiding which index to use

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 :-)

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

Zizi