BBI Edwin Punzalan wrote:
Hi.
1) chatlogs rows increases every now and then (its in a live environment)
and currently have 538,696 rows
OK, so as a rule of thumb I'd say if you were fetching less than 5000
rows it's bound to use an index. If more than 50,000 always use a
seqscan, otherwise it'll
reSQL except setting fsync to false.
Thanks for taking a look at our problem. :D
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 6:17 PM
To: BBI Edwin Punzalan
Cc: [EMAIL PROTECTED]
Subject: Re: FW: [PERFORM] FW: Index usage
BBI Edwin Pun
BBI Edwin Punzalan wrote:
Thanks, Tim.
I tried adding an upper limit and its still the same as follows:
==
db=# explain analyze select date from chatlogs where date>='11/24/04';
NOTICE: QUERY PLAN:
Index Scan using chatlogs_date_idx on chatlogs (cost=0.00..145.72 rows=37
width=4) (act
