Re: index problem (uses one index but not the other)

Yes, there are 42000+ records with order_id = 0, no other order_id is present in more than 10 records.<br /><br /> Is
thereany simple way to solve this problem without going to 7.2? (I'd rather go to 7.3 directly in a month or two).<br
/><br/> --Maurice<br /><br /> PS: Thanks for always being there for 'us', the plain users. <br /><br /><br /> Tom Lane
wrote:<br/><blockquote cite="mid:9810.1018936158@sss.pgh.pa.us" type="cite"><pre wrap="">Maurice Balick <a
class="moz-txt-link-rfc2396E"href="mailto:balm@smiley.com"><balm@smiley.com></a> writes:<br /></pre><blockquote
type="cite"><prewrap="">The weird thing is that this used to work (i.e. trans_oid_idx was used)<br />when there was
about200000 records (about 1/3 of now). Also, there is <br />about<br />9000 distinct values of account_id, but about
300000values of order_id.<br /></pre></blockquote><pre wrap=""><br />What's the most common value in each case?<br
/><br/></pre><blockquote type="cite"><pre wrap="">(I am running Postgresql 7.1.3 on Redhat 7.1)<br
/></pre></blockquote><prewrap=""><br />7.2 is less likely to be fooled when the most common value is much more<br
/>commonthan the rest ...<br /><br />            regards, tom lane<br /><br />---------------------------(end of
broadcast)---------------------------<br/>TIP 4: Don't 'kill -9' the postmaster<br /><br />.<br /><br
/></pre></blockquote><br/>