Mark Kirkwood wrote:
Kurt Overberg wrote:
work_mem = 100MB # when I ran the original
query, this was set to 1MB, increased on Mark Kirkwood's advice,
seemed to help a bit but not really
For future reference, be careful with this parameter, as *every*
connection will use this much memory for each sort or hash (i.e it's not
shared and can be allocated several times by each connection!)...yeah, I
know I suggested increasing it to see what effect it would have :-).
This is however a parameter that can be set on the fly for the specific
query.
Joshua D. Drake
And I'd agree with Steiner and others, looks like caching effects are
the cause of the timing difference between production and the mac!
Cheers
Mark
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
