Re: Avoiding a seq scan on a table.

LWATCDR  writes:
> Anyway I put in the tree indexes and I am still getting a seq scan.

> Aggregate  (cost=12.12..12.13 rows=1 width=0)
>   ->  Result  (cost=0.00..12.12 rows=1 width=0)
>         One-Time Filter: NULL::boolean
>         ->  Seq Scan on issuetracking  (cost=0.00..12.12 rows=1 width=0)
>               Filter: (((issue_target)::text = 'david'::text) OR
> ((manager)::text = 'david'::text))

You should worry about making the query correct before you worry about
making it fast.  That constant false one-time filter is a red flag...
looks like you forgot the difference between "IS NULL" and "= NULL".

			regards, tom lane