| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Javier Carlos <fjcarlos(at)correo(dot)insp(dot)mx> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: SELECT with MANY tables |
| Date: | 2003-11-24 19:28:15 |
| Message-ID: | 20031124112711.C84194@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, 24 Nov 2003, Javier Carlos wrote:
>
> Please enter a FULL description of your problem:
> -------------------------------------------------
> When I make a SELECT with many tables (more than 12), postgresql eats all my
> %CPU and I've waited more than 1 hour and stays the same. The weird thing is
> that with 10 tables the same select with the same joins only takes about 5
> seconds. First I thought that It was a problem related with one specific table,
> but I've changed in the SELECT the tables and while the number of tables remains
> less than 12 all is ok.
As a question, does the query work if you SET geqo=off; or SET
geqo_threshold=<some higher number, say 20>?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-11-24 19:32:31 | Re: Fwd: Solaris build of 7.4 problem with --enable-thread-safety |
| Previous Message | Seum-Lim Gan | 2003-11-24 16:50:24 | Fwd: Solaris build of 7.4 problem with --enable-thread-safety |