A composite index combines two or more columns so the database can support a recurring query pattern. Read it as a fossilized record of what the application searches or sorts together, not merely as an optimization detail. section 7.6
Reading indexes as product behavior
A table may define indexes such as [startTime, endTime, status], [userId, status, startTime], and [eventTypeId, status]. The useful question is not only “what columns are indexed?” but “which product surface repeatedly needs these columns together?” Review each index as a clue to a common WHERE clause, then connect that clause to the user-facing behavior it makes fast. section 7.6



