StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12566879
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-24T14:16:58.310
FavoriteCount
0
LastActivityDate
2012-09-24T14:22:04.627
LastEditDate
2012-09-24T14:22:04.627
LastEditorUserId
119634
OwnerUserId
119634
ParentId
12565790
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The explain plans are different: a single <code>MIN</code> or <code>MAX</code> will produce a <code>INDEX FULL SCAN (MIN/MAX)</code> whereas when the two are present you will get an <code>INDEX FULL SCAN</code> or a <a href="http://docs.oracle.com/cd/E11882_01/server.112/e25789/indexiot.htm#sthref320" rel="nofollow"><code>FAST FULL INDEX SCAN</code></a>. To understand the difference, we have to look for a description of a <a href="http://docs.oracle.com/cd/E11882_01/server.112/e25789/indexiot.htm#CNCPT88838" rel="nofollow"><code>FULL INDEX SCAN</code></a>: <blockquote> In a full index scan, the database reads the entire index in order. </blockquote> In other words, if the index is on a <code>VARCHAR2</code> field, Oracle will fetch the first block of the index that would contain for example all entries that start with the letter "A" and will read block by block all entries alphabetically until the last entry ("A" to "Z"). Oracle can process in this way because the entries are sorted in a binary tree index. When you see <code>INDEX FULL SCAN (MIN/MAX)</code> in an explain plan, that is the result of an optimization that uses the fact that since the entries are sorted, you can stop after having read the first one if you are only interested by the <code>MIN</code>. If you are interested in the <code>MAX</code> only, Oracle can use the same access path but this time starting by the last entry and reading backwards from "Z" to "A". As of now, a <code>FULL INDEX SCAN</code> has only one direction (either forward or backward) and can not start from both ends simultaneously, this is why when you ask for both the min and the max, you get a less efficient access method. As suggested by other answers, if the query needs critical efficiency, you could run your own optimization by searching for the min and the max in two distinct queries.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSelecting both MIN and MAX From the Table is slower than expected
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVincent Malgrat
UserOwnerUserId
1. USVincent Malgrat
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.