From: Tom Lane <tgl@sss.pgh.pa.us>
To: stefan@konink.de
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #8130: Hashjoin still gives issues
Date: Wed, 01 May 2013 11:10:52 -0400
Message-ID: <3469.1367421052@sss.pgh.pa.us> (raw)
In-Reply-To: <E1UXWS7-0007V8-N2@wrigleys.postgresql.org>
References: <E1UXWS7-0007V8-N2@wrigleys.postgresql.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
stefan@konink.de writes:
> By setting "set enable_hashjoin = off;" performance in our entire
> application increased 30 fold in throughput, which was a bit unexpected but
> highly appreciated. The result of the last query:
At least in this example, the query appears to be fully cached and so
you would need a random_page_cost near 1 to reflect the system's
behavior properly. If your DB fits mostly in RAM, adjusting the cost
parameters is a much better idea than fooling with the enable_
parameters.
> What can we do to provide a bit more of information?
https://wiki.postgresql.org/wiki/Slow_Query_Questions
There is no particularly good reason to think this is a bug; please
take it up on pgsql-performance if you have more questions.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
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: tgl@sss.pgh.pa.us, stefan@konink.de, pgsql-bugs@postgresql.org
Subject: Re: BUG #8130: Hashjoin still gives issues
In-Reply-To: <3469.1367421052@sss.pgh.pa.us>
* 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