Richard Huxton wrote:
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 |
Title: Re: [PERFORM] Deceiding which index to use
- Re: [PERFORM] Deceiding which index to use Mezei Zoltán
- Re: [PERFORM] Deceiding which index to use Richard Huxton
- Re: [PERFORM] Deceiding which index to use Mezei Zoltán
- Re: [PERFORM] Deceiding which index to use Richard Huxton