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
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
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2002-10-07 14:49:32|
|Subject: Re: postmaster will not start with stale lockfile but not report why |
|Previous:||From: Masaru Sugawara||Date: 2002-10-07 12:04:59|
|Subject: Re: problem with composed types in plpgsql|