Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3937

Select count(*) scans all the rows (and is therefore slow with big tables), is the amount of rows not available/known for example in index ?

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Store
    • None
    • Any
    • Performance

    Description

      Create table with 5000000 rows. Create index on unique ID. Select count on such table is going to take quite some time.

      Shouldn't the index contain amount of indexed rows and the value taken from there ?

      Additionally, queries of the form select count from table where col1=value; take lots of time (depending on amount of rows satisfying WHERE clause) even if index on col1 exists. Isn't it possible to find first and last occurence in the index, and then calculate amount of rows more effectively then scanning through all of them ?

      Attachments

        Activity

          People

            Unassigned Unassigned
            s0m3body Martin Hajduch
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: