From: Stef <svb@ucs.co.za>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Query kills machine.
Date: Wed, 25 Aug 2004 16:30:41 +0200
Message-ID: <20040825163041.716d2103@svb.ucs.co.za> (raw)
In-Reply-To: <4015.1093361011@sss.pgh.pa.us>
References: <20040824103240.4d909777@svb.ucs.co.za>
<412B05A2.8070301@familyhealth.com.au>
<20040824153014.2a11d228@svb.ucs.co.za>
<4015.1093361011@sss.pgh.pa.us>
Tom Lane mentioned :
=> Not if you haven't got the RAM to support it :-(
=>
=> Another thing you might look at is ANALYZEing the tables again after
=> you've loaded all the new data. The row-count estimates seem way off
=> in these plans. You might need to increase the statistics target,
=> too, to get better plans.
Thanks Tom, Christopher and Magnus!
I tested this, and found the correct sort_mem setting for my situation.
I'm testing a new default_statistics_target setting.
This is something I never considered.
Kind Regards
Stefan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: svb@ucs.co.za, tgl@sss.pgh.pa.us
Subject: Re: Query kills machine.
In-Reply-To: <20040825163041.716d2103@svb.ucs.co.za>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox