| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | stefan(at)konink(dot)de |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8130: Hashjoin still gives issues |
| Date: | 2013-05-01 15:10:52 |
| Message-ID: | 3469.1367421052@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
stefan(at)konink(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-05-01 15:12:28 | Re: Re: [BUGS] BUG #8128: pg_dump (>= 9.1) failed while dumping a scheme named "old" from PostgreSQL 8.4 |
| Previous Message | Stefan Kaltenbrunner | 2013-05-01 14:37:40 | Re: Re: [BUGS] BUG #8128: pg_dump (>= 9.1) failed while dumping a scheme named "old" from PostgreSQL 8.4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan de Konink | 2013-05-01 15:44:54 | Re: [BUGS] BUG #8130: Hashjoin still gives issues |
| Previous Message | ktm@rice.edu | 2013-05-01 14:12:36 | Re: Deterioration in performance when query executed in multi threads |