From: | "Norbert Zoltan Toth" <Norbert(dot)Zoltan(dot)Toth(at)cern(dot)ch> |
---|---|
To: | "Mitch Vincent" <mvincent(at)cablespeed(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Index usage question - Norbert |
Date: | 2001-09-04 22:25:50 |
Message-ID: | 004b01c13590$8d14adf0$11278a89@cern.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
(Sorry for reposting...)
> You said you enter some rows, but how many rows got returned by your
query?
You're right, it does make all the difference. With only a few rows,
indexing is somehow used in the first case only (for my example), but with
larger tables index scan is used in both ways.
Many thanks,
Norbert
>
> Though I'm not sure, PG might not treat that 1 as the integer 1, since
it's
> in single quotes.. The index was on an integer field, perhaps that is part
> of the problem too...
>
> -Mitch
>
> > I have experienced the following problem, maybe they are related:
> >
> > I create a table with
> > create table test (id int, name char(10));
> >
> > then I create an index on it with
> > create index test_idx on test (id);
> >
> > After populating my table, the query
> > select id from test where id='1';
> >
> > uses index scan.
> >
> > However when I only create the index AFTER inserting rows into the
table,
> > the index is not being used for the evaluation,
> > even if I run vacuum / vaccum analyze on test;
> >
> > I would also appreciate some help with this.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-09-04 23:14:40 | Re: embedded SQL cursos declare fails |
Previous Message | Norbert Zoltan Toth | 2001-09-04 22:20:32 | Re: Index usage question |