From: Gregory Stark <gsstark@mit.edu>
To: Florian Weimer <fweimer@bfk.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Abysmal hash join
Date: 11 Sep 2006 20:56:27 -0400
Message-ID: <87k649q4w4.fsf@stark.xeocode.com> (raw)
In-Reply-To: <82sliyweny.fsf@mid.bfk.de>
References: <821wqiy0oc.fsf@mid.bfk.de>
<22641.1157984931@sss.pgh.pa.us>
<82wt8awi21.fsf@mid.bfk.de>
<3204.1157989198@sss.pgh.pa.us>
<82sliyweny.fsf@mid.bfk.de>
Florian Weimer <fweimer@bfk.de> writes:
> I've done that. Fortunately, ANALYZE time didn't increase by that
> much, compared to the default (by just a factor of 10).
With really high stats times you also have to keep an eye on planning time.
The extra data in the stats table can cause planning to take longer.
--
greg
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: gsstark@mit.edu, fweimer@bfk.de, tgl@sss.pgh.pa.us
Subject: Re: Abysmal hash join
In-Reply-To: <87k649q4w4.fsf@stark.xeocode.com>
* 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