From: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
---|---|
To: | |
Cc: | Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: RAID arrays and performance |
Date: | 2008-09-19 16:22:51 |
Message-ID: | 48D3D1DB.5010803@mark.mielke.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Matthew Wakeling <matthew(at)flymine(dot)org> writes:
>> In order to improve the performance, I made the system look ahead in the
>> source, in groups of a thousand entries, so instead of running:
>> SELECT * FROM table WHERE field = 'something';
>> a thousand times, we now run:
>> SELECT * FROM table WHERE field IN ('something', 'something else'...);
>> with a thousand things in the IN. Very simple query. It does run faster
>> than the individual queries, but it still takes quite a while. Here is an
>> example query:
>>
Have you considered temporary tables? Use COPY to put everything you
want to query into a temporary table, then SELECT to join the results,
and pull all of the results, doing additional processing (UPDATE) as you
pull?
Cheers,
mark
--
Mark Mielke <mark(at)mielke(dot)cc>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2008-09-19 18:25:28 | Re: why does this use the wrong index? |
Previous Message | Matthew Wakeling | 2008-09-19 15:25:30 | Re: RAID arrays and performance |