| From: | Deepa <kdeepa(at)midascomm(dot)com> | 
|---|---|
| To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> | 
| Cc: | <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: Creating index does not make any change in query plan. | 
| Date: | 2003-02-17 09:13:40 | 
| Message-ID: | Pine.LNX.4.33.0302171439040.10110-100000@ws1154.midascomm.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Mon, 17 Feb 2003, Shridhar Daithankar wrote:
> It is very simple. Unless the indexed field and the field in query does not 
> match exactly in type, the planner does not consider using index.
Actually the indexed field is an bigint field. But when a query plan is 
did on a selection using indexed field as a string it actually uses the 
index. Otherwise, it does a ordinary query plan  (i.e an non indexed query 
plan).
> 
> What would be good in planner is to have field promotion like in C/C++, 
> smallint->bigint->float->double as and when required. That would help a hell 
> lot many people..
> 
Will you please tell me how does the field promotion helps in planner.
> Bye
>  Shridhar
> 
--
Bye,
Deepa. K
--
Engineer,
Network Management System,
Midas Communication Technologies private Ltd,
Chennai.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2003-02-17 09:32:47 | Re: Creating index does not make any change in query plan. | 
| Previous Message | Ken Guest | 2003-02-17 09:12:45 | Re: natural sort order |