The plan showed that Postgres did the proper cast on the timestamp. I
think part of the problem is that I need to increase the memory
allocated to effective_cache_size for the optimizer choose the proper
method. (Thanks to Richard Huxton for help.) I've read that if it
doesn't have enough ra
I apologize for the following stupid question. I have been doing some
searching and haven't found anything really helpful.
The problem is that postgres (7.4.2) keeps choosing to do a sequential
scan on a table when an index scan would be significantly faster.
The queries that I'm using look at
