Re: [PERFORM] PostgreSQL upgraded to 8.2 but forcing index scan on query produces faster

uery has started? The other part of the solution is bit concerning. I had to do a 'dump and load' (and vacuum analyze) to get the planner to work correctly even after I rewrote the query. FYI I had run 'VACUUM ANALYZE' (and sometimes 'REINDEX TABLE x') between e

[PERFORM] PostgreSQL upgraded to 8.2 but forcing index scan on query produces faster

now() group1_id| character varying(64)| group2_id| text | group3_id| text | void | boolean | not null default false hash | boolean | not null default false component| boolean

[PERFORM] Forcing index scan on query produces 16x faster

idth=175) (actual time=0.077..0.085 rows=1 loops=1) Index Cond: (id = 'net/Console/Employee/Day End Time'::text) -> Index Scan using sales_tranzdate_index on sales s (cost=0.01..1825.27 rows=22530 width=12) (actual time=0.074..1.945 r