We're experiencing a little problem with one of our queries.
It isn't using an index specially created for it. When we
disable seq scans with psql, we can ensure the query finishes
much faster than without using index, as it should be.
So, whats the best procedure in this case, but when have a
JDBC based client? Do we mess around with planner
settings even when all other queries are using the best
index for them?
Is it safe (but some may find ugly) to issue a command to
disable seq scanning from the java side?
Since we're using the pooled connection classes that comes
with the JDBC3 driver, once a connection is got from the pool,
do we need to explicitly set seq scanning to true? This is
assuming the later option is the more recommended one...
pgsql-jdbc by date
|Next:||From: Sean Shanny||Date: 2004-04-01 20:36:24|
|Subject: Re: disabling seq scans|
|Previous:||From: Rajat Katyal||Date: 2004-04-01 13:19:55|
|Subject: JDBC driver returning the numeric dataype size as -1|