| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthew Wakeling <matthew(at)flymine(dot)org> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, andy(at)flymine(dot)org |
| Subject: | Re: Possible bug in PostgreSQL query planner |
| Date: | 2002-10-07 14:42:36 |
| Message-ID: | 23584.1034001756@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Matthew Wakeling <matthew(at)flymine(dot)org> writes:
> I have encountered what seems to be a bad decision made by the query
> planner, on a quite simple query. I have attached a shell script which
> creates a large (180MB) sql script, to demonstrate the problem.
These queries are forcing the join order; see
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/explicit-joins.html
The second query forces a bad join order.
Whether this is a bug or a feature depends on your perspective; for now,
it's defined to be a feature ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-07 14:49:32 | Re: postmaster will not start with stale lockfile but not report why |
| Previous Message | Masaru Sugawara | 2002-10-07 12:04:59 | Re: problem with composed types in plpgsql |