Re: [BUGS] Bad planner decision in Postgres

2005-02-02 Thread Matthew Wakeling
> Matthew Wakeling <[EMAIL PROTECTED]> writes: > > [ snip... ] > > If we remove the limit, then the planner switches to this query plan: > > > Limit (cost=156.24..156.26 rows=10 width=14) > > ... which still has a limit. I think you have made several cut-and-paste > errors here, because the plan

Re: [BUGS] Bad planner decision in Postgres

2005-02-01 Thread Tom Lane
Matthew Wakeling <[EMAIL PROTECTED]> writes: > [ snip... ] > If we remove the limit, then the planner switches to this query plan: > Limit (cost=156.24..156.26 rows=10 width=14) ... which still has a limit. I think you have made several cut-and-paste errors here, because the plans you are exhib

[BUGS] Bad planner decision in Postgres

2005-01-31 Thread Matthew Wakeling
Good afternoon. I think I may have found a bad planner decision in Postgres. In essence, I have a table that is well-sorted, and has an index on the sort column. I wish to retrieve all rows from the table that have a column value greater than X, or some other condition (which is also indexed and w