From: | Peter Keller <peter(dot)keller(at)bvv(dot)bayern(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Problems with genetic optimizer |
Date: | 2000-10-24 12:42:47 |
Message-ID: | 39F583C6.7FDE0CE9@bvv.bayern.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I generated a table with a column type 'box', inserted some values and
created an index (ops_box) on that column, run a vacuum and looked with
the command EXPLAIN if the select will use the index.
And the result was very astonishing:
if I had inserted 120000 elements postgres will _NOT_ use the index, if
I had inserted 100000 elements postgres will use the index!
When I set the sequential search off ('set enable_seqscan off;')
postgres is using the index in both cases.
Has someone any idea what to do?
Peter
--
Bezirksfinanzdirektion Muenchen
Vermessungsabteilung
.........................................................
Peter Keller : Tel: (+49) 089-2190-2594
Vermessungsrat : Fax: (+49) 089-2190-2459
Alexandrastr. 3 : mailto:Peter(dot)Keller(at)bvv(dot)bayern(dot)de
80538 Muenchen : web: http://www.bayern.de/vermessung
From | Date | Subject | |
---|---|---|---|
Next Message | danyele | 2000-10-24 13:10:03 | phpPgAdmin |
Previous Message | Tom Lane | 2000-10-24 12:39:44 | Re: PL/Perl compilation error |