how the planner decides between bitmap/index scan

From: Scara Maccai <m_lists(at)yahoo(dot)it>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: how the planner decides between bitmap/index scan
Date: 2009-05-19 08:30:32
Message-ID: 624832.94511.qm@web24603.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi,

does the planner know how "scattered" rows are? If yes: where is this info stored?

I'm asking because it looks to me that not only the number of rows, but also how data is on disk (more or less sequential) is used to determine what type of index scan (bitmap/regular) has to be used...

but in the docs:
http://www.postgresql.org/docs/8.4/static/using-explain.html
I've found only "there are so few that the extra cost of sorting the row locations is not worth it", which would mean that only the number of rows is actually used to choose between the two index access methods.

Can someone explain?

Thank you

Browse pgsql-general by date

  From Date Subject
Next Message Sebastien FLAESCH 2009-05-19 08:39:20 INTERVAL SECOND limited to 59 seconds?
Previous Message Sebastien FLAESCH 2009-05-19 08:08:37 INTERVAL data type and libpq - what format?