2 questions:
1) Have you recently run an analyze?
2) Are you sure that an index scan would be more efficient than a seq
scan? (are less than 25% of the records selected) I don't know the
break-off boint in the query optimizer, but it may be more efficient on
that table to read the whole thing.
Try coercing your constants to int8 explicitly:
... WHERE int8col = 42::int8;
See the archives for more info about this.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the
Mauro Flores ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Index using INT8 data type is ignored
Long Description
I have some tables on my data base with index and primary keys over int8(bigint) data
type columns. Postgress
