Hi. Thanks for your reply. The date column data type is date already. :D
-Original Message-
From: Iain [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 01, 2004 12:00 PM
To: BBI Edwin Punzalan; 'gnari'; [EMAIL PROTECTED]
Subject: Re: [PERFORM] FW: Index usage
If it
TICE: QUERY PLAN:
Seq Scan on chatlogs (cost=0.00..27252.86 rows=271882 width=212) (actual
time=12.24..13419.36 rows=257137 loops=1)
Total runtime: 13573.70 msec
EXPLAIN
=
-Original Message-
From: gnari [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 01, 2004
Hi, what do you mean by increasing the statistics on the date column?
We never had any upgrade on it.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of gnari
Sent: Thursday, November 25, 2004 3:13 AM
To: BBI Edwin Punzalan; [EMAIL PROTECTED]
Subject: Re
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
Yes, the database is being vacuum-ed and analyzed on a daily basis.
Our version is 7.2.1
-Original Message-
From: gnari [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 4:35 PM
To: BBI Edwin Punzalan; [EMAIL PROTECTED]
Subject: Re: [PERFORM] FW: Index usage
From: &quo
s=1)
Total runtime: 4282.81 msec
==
How come a query on the current date filter uses an index and the others
does not? This makes indexing to speed up queries quite difficult.
-Original Message-
From: Leeuw van der, Tim [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2
Hi everyone,
Can anyone please explain postgres' behavior on our index.
I did the following query tests on our database:
db=# create index chatlogs_date_idx on chatlogs (date);
CREATE
db=# explain select date from chatlogs where date>='11/23/04';
NOTICE: QUERY PLAN:
Index