<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<small>Richard Huxton wrote:</small>
<blockquote cite="mid:45F182B7(dot)30507(at)archonet(dot)com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="MS Exchange Server version 6.5.7226.0">
<title>Re: [PERFORM] Deceiding which index to use</title>
<!-- Converted from text/plain format -->
<p><font size="2">There is a cost to increasing the stats values,
otherwise it'd already<br>
be set at 1000. In your case I'm not sure if 100-200 vs 8-9 messages is<br>
enough to skew things. Only one way to find out...<br>
</font></p>
</blockquote>
<small>Well, I tried. The situation is:<br>
<br>
- when I look for a subscriber which the planner thinks to have more
messages --> it uses the index on crd<br>
- when I look for a subscriber which the planner thinks to have less
messages --> it uses the index on subscriber_id<br>
<br>
I think that's OK, even if it still don't do what I really would like
to see it do :-)<br>
<br>
Thanks for all your help, maybe I know a little bit more about
poostgresql than before.<br>
<br>
Zizi</small><br>
</body>
</html>