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-

[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

[BUGS] Possible bug in PostgreSQL query planner

2002-10-07 Thread Matthew Wakeling
x-gnu, compiled by GCC 2.95.4 PostgreSQL was installed as a Debian package. The machine is a Athlon XP1900, with 512MB of RAM, a 40GB hard drive. Kernel: Linux 2.4.19-686 libc6: 2.2.5-14.1 Matthew Wakeling #!/bin/bash echo "create table jointest3_1 (keya int, infoa int);" echo "crea