We re-tested these settings a few times after our initial test and realized that the execution time I posted was shewed, because the execution plan was cached after the initial run. Subsequent executions ran in a little over a second.
There ended up being no significant saving by setting these para
On Fri, May 24, 2013 at 3:44 PM, wrote:
> Total runtime: 1606.728 ms 1.6 seconds <- very good response time
> improvement
>
> (7 rows)
>
> Questions:
>
> Any concerns with setting these conf variables you recommended; work_mem,
> random_page_cost dbserver wide (in postgresql,conf)?
>
> Thanks so
)? Thanks so much!!!
---- Original Message
Subject: Re: [GENERAL] [PERFORM] Very slow inner join query Unacceptable
latency.
From: Scott Marlowe <scott.marl...@gmail.com>
Date: Thu, May 23, 2013 11:16 pm
To: fburg...@radiantblue.com
Cc: Jaime Casanova <ja...@2ndquadrant.com
Looking at the execution plan makes me wonder what your work_mem is
set to. Try cranking it up to test and lowering random_page_cost:
set work_mem='500MB';
set random_page_cost=1.2;
explain analyze select ...
and see what you get.
--
Sent via pgsql-performance mailing list (pgsql-performance@
