From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kishore B <kishorebh@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why Index is not working on date columns.
Date: Tue, 25 Oct 2005 14:01:04 -0400
Message-ID: <18598.1130263264@sss.pgh.pa.us> (raw)
In-Reply-To: <42567e060510250804y3329c901l21770d887dfcde42@mail.gmail.com>
References: <42567e060510250147j582ce648p3ceef8e4376975be@mail.gmail.com>
<13279.1130247515@sss.pgh.pa.us>
<42567e060510250804y3329c901l21770d887dfcde42@mail.gmail.com>
Kishore B <kishorebh@gmail.com> writes:
>> I surmise that you are testing on toy tables and extrapolating to what
>> will happen on larger tables.
>>
> These tables participating here contain more than 8 million records as of
> now, and on every day, 200K records, will add to them.
In that case, have you ANALYZEd the tables lately? The planner's cost
estimates correspond to awfully small tables ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, kishorebh@gmail.com
Subject: Re: Why Index is not working on date columns.
In-Reply-To: <18598.1130263264@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox