Indexes and querys

[Josué Maldonado]

Hello list,

I have a table with an index in a foreing key field (int4), if I do
select from pedido where prvdfk=3, explain says is using seq scan to
access it. I noticed all my querys runs in that way, except in the
querys where the PK field (unique type index) is included in the where
clause.

Is this the rigth way that postgresql works ?, is there something I
should check in my configuration?

According to select version() this is the my one:
PostgreSQL 7.3.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
20020903 (Red Hat Linux 8.0 3.2-7)

Thanks in advance

--
Josué Maldonado.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Peter Eisentraut]

Josué Maldonado writes:

I have a table with an index in a foreing key field (int4), if I do
select from pedido where prvdfk=3, explain says is using seq scan to
access it. I noticed all my querys runs in that way, except in the
querys where the PK field (unique type index) is included in the where
clause.

PostgreSQL will choose to use an index when it thinks it will be faster,
but this is not always the case. If you want to learn more about how
indexes work or how to evaluate query performance, please read the
documentation.

--
Peter Eisentraut pe*****@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org