> Any help with this problem would be greatly appreciated. After
> executing the following query, the postgres backend server process that
> is executing the query grows in size until it consumes well over 200 MB
> and takes several minutes to finish:
>
> select mlno from table where
> (area='01' and sub_area='01') or
> (area='01' and sub_area='02') or
> (area='01' and sub_area='03') or
> (area='01' and sub_area='04') or
> (area='07' and sub_area='01') or
> (area='07' and sub_area='02') or
> (area='07' and sub_area='03') or
> (area='08' and sub_area='01') or
> (area='08' and sub_area='03') or
> (area='09' and sub_area='01') or
> (area='09' and sub_area='02') or
> (area='04') or
> (area='05') or
> (area='06') or
> (area='99');
We have problems processing a large number of OR's. 6.6 will be better
in this area.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
