There are perfectly valid reasons why postgres uses a sequence scan as
opposed to an index scan.
http://www.postgresql.org/docs/faqs/FAQ.html
That being said, the reason I asked if you had vacuumed the database
lately is that that is the only way to update the planner statistics.
So please vacuum analyze the entire db, if it then doesn't use an index
scan you can try disabling sequence scans in the configuration file.
Dave
On Wed, 2003-09-10 at 09:31, Paul Thomas wrote:
> On 09/09/2003 18:39 Barry Lind wrote:
> > Rod,
> >
> > That was tried once and needed to be pulled out. That change ended up
> > breaking some code since there are some circumstances where '5' is not
> > the same as 5 in the parser. I don't remember the details but they
> > should be in the maillist archives (or the cvs commit message for the
> > revert on the change).
> >
> > thanks,
> > --Barry
> >
> > PS. Because of having tried and failed to fix this in the driver
> > before, I am gun shy on trying a fix again at the driver level. The
> > server is the proper place for this to be fixed. And I think it is in
> > 7.4, but haven't verified that myself.
>
> Is there any way we could find out for definite? Until this index/type
> cast issue is sorted out I don't see any way that PostgreSQL can even be
> considered ready for enterprise use. EJB/CMP is an important enterprise
> technology and int8 index columns are not unknown in big company databases.
--
Dave Cramer <Dave@micro-automation.net>
