From: | sanjay tumula <stumula(at)comcast(dot)net> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | performance problem |
Date: | 2005-04-15 14:24:52 |
Message-ID: | 425FCEB4.3050802@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ruud,
thanx for your reply.
I am narrowing down on the problem...found that Suse 9.2 has a lot of
memory related problems.
reverted back to 9.1 and rebuilding the app..will post an update.
you suggestion will not work for me though...i need to check existing
records and create new records..which cannot be done on one table.
unless you are going thru hoops and doing a lot of text processing....at
which point why do you need a database :-)
also here is something interesting that i found regarding IN vs = on a
btree index.
select col1, col2
from table1
where col1 in ( 1,2,3)
;
this comes right back
select col1, col2
from table2
where col1 = 1
;
comes right back.
select col1,col2
from table2
where col1
IN
(
select col1 from table2
where col1 between 1 and 2
)
;
this takes a while....
which tells me IN is still not optimized..or am i missing something?
lastly..please post to the forum and not directly to my email....so the
community can see the 'whole' picture.
thanx
Sanjay
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-04-15 16:58:02 | Re: cost of empty fields |
Previous Message | Enrico Weigelt | 2005-04-15 14:22:07 | cost of empty fields |