On Mon, 2008-09-08 at 09:16 -0700, Matt Smiley wrote:
> Hi Kiran,
>
> You gave great info on your problem.
>
> First, is this the query you're actually trying to speed up, or is it a
> simplified version? It looks like the optimizer has already chosen the best
> execution plan for the given qu
BTW: Have just tried "clean" (without any foreign keys constraints)
peformance of
"delete from tbl where field not in (select)"
vs
"create temporary table tmp(id) as select distinct field from tbl; delete
from tmp where id in (select); delete from tbl where field in (select id
from tmp)".
both tbl
On Thu, 9 Oct 2008, Scott Carey wrote:
Sure, the processor should be faster, but Athlon64s / Opterons are very
sensitive to the RAM used and its performance and tuning. So, you should
find some basic CPU benchmarks and RAM benchmarks -- you'll want to
measure latency as well as bandwidth. Athl
On Thu, 9 Oct 2008, Craig James wrote:
Did you do an ANALYZE on the new database after you cloned it?
He ran "vacuumdb -f -z", the -z does an analyze. Also, he's getting
nearly identical explain plans out of the two systems, which suggests the
stats are similar enough in the two cases.
--
