By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,374 Members | 2,014 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,374 IT Pros & Developers. It's quick & easy.

Indexes and querys

P: n/a
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

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
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

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.