| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Marco Vezzoli <marco(dot)vezzoli(at)st(dot)com>, sql <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: postgres 7.1.3: why does the query plan ignore indexes? |
| Date: | 2003-08-27 04:27:20 |
| Message-ID: | 8860.1061958440@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>> Should we consider adding some warning when someone creates an index on
>>> an int2 column?
>>
>> I don't think so. Better to expend our energy on solving the
>> fundamental problem.
> I am thinking _until_ we fix the problem. Is it actually hard to add?
Why int2 in particular? And not int8? float4? Or numeric, float8,
or int4 in the wrong contexts? How about bpchar or varchar?
I figure we can waste at least as much time arguing about when/where/why
to issue warnings as it will take to solve the real problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kumar | 2003-08-27 07:18:15 | How to return a record set from function. |
| Previous Message | Bruce Momjian | 2003-08-27 04:22:08 | Re: postgres 7.1.3: why does the query plan ignore indexes? |