| From: | Christof Petig <christof(at)petig-baender(dot)de> |
|---|---|
| To: | Justin Clift <aa2(at)bigpond(dot)net(dot)au> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Query Planning time increased 3 times on 7.1 compared to 7.0.3 |
| Date: | 2001-03-05 14:00:47 |
| Message-ID: | 3AA39C0E.9FF0E4C2@petig-baender.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Clift wrote:
> Hi Christof,
>
> I'm not aware of the problem with int2 indexes collapsing. Can you give
> me some more info, and I'll put it on the techdocs.postgresql.org
> website.
Oh, I'm sorry for my strange wording.
I said that the index search collapses to a sequential scan if you do not
cast the number to int2.
Because an int2 index is not used to look up an int4.
And untyped numbers are int4 or numeric the int2 index is never used unless
explicitely specified (by a type cast).
Yes this is a known bug in PostgreSQL 7.1 and below. Hopefully this will
get addressed in 7.2?
Why don't I code it? I'm busy working on ecpg (dyn. SQL) at the moment.
Christof
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christof Petig | 2001-03-05 15:07:04 | Re: Query Planning time increased 3 times on 7.1 compared to 7.0.3 |
| Previous Message | Hannu Krosing | 2001-03-05 12:27:45 | Re: Oops! Its bug in parser???? |