in case that one has a table R(att0 int4, att1 int4), an index on att1 and a query selecting only att1 whith a range condition over att1, then the optimal access path for a rdbms would be "INDEX ONLY SCAN", which means scan only the index, and not the relation (all the needed information exists in index, because the select clause has only the att1 attribute). This access path is selected in this case by Oracle.
As far as i can see, postgresql select a simple "INDEX SCAN using index" on table.
Is there any tuning that one has to do, in order to make postgresql's optimizer to select "INDEX ONLY SCAN" ? Or postgresql doesn't support this feature at all?