IN
Here it will do an index scan if and only if I use the '=' operator. If I
use like with the % at the end of the string or EVEN if I have no wild card
at all... it still does a seq scan. If anyone has any advice on how to
get
g wrong? The data is the same type so I don't need to
cast, right? What other tricks are there to get the query planner to
be smart?
Orion
Here's my exact table structure:
fdb=# \d mfps_orderinfo_435
Table "mfps_orderinfo_435"
Hello. I need help tracking down a crash bug. I'm running 8.2.7
I've had my database go into recovery mode three times so far today under
user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave
a few processes behind like this
postgres 22318 0.0 0.0 45724 1272 ?S
Hello. I need help tracking down a crash bug. I'm running 8.2.7
I've had my database go into recovery mode three times so far today under
user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave
a few processes behind like this
postgres 22318 0.0 0.0 45724 1272 ?S
at fe-connect.c:541
#9 0x0040a1db in main (argc=1, argv=0x7fbfffe058) at startup.c:183
(gdb)
--
Orion Henry <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
