Re: [ADMIN] Index Scan Backward

2003-01-28 Thread Luca Fabbro
At 10.17 27/01/2003 -0500, you wrote: Limit (cost=0.00..1003.36 rows=1 width=454) (actual time=806.78..2097.61 rows=1 loops=1) - Nested Loop (cost=0.00..392651.18 rows=391 width=454) (actual time=806.77..2097.59 rows=2 loops=1) - Index Scan Backward using

[ADMIN] Index Scan Backward

2003-01-27 Thread Luca Fabbro
Hi all, I'm experiencing a strange problem in the usage of indexes for query optimization. I'm runnig a forum application that uses a PostgreSQL DB. The version on the DB is 7.2.3 but I've also tested it under 7.3.1 but I had no luck :( The problem is always the same. Linux distro is Slackware

Re: [ADMIN] Index Scan Backward

2003-01-27 Thread Luca Fabbro
At 09.39 27/01/2003 -0500, you wrote: Luca Fabbro [EMAIL PROTECTED] writes: It seems that the problem is in the Backward scan of the index :( It looks like a pretty reasonable plan to me. Could we see the output of EXPLAIN ANALYZE, not just EXPLAIN? Thanks Tom for your interest. It looks