BIND 10 #1899: performance issue of SQLite3 "iterate" query (w/ or w/o NSEC3)

[BIND 10 Development]

#1899: performance issue of SQLite3 "iterate" query (w/ or w/o NSEC3)
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20121009
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  6
                   Keywords:         |           Total Hours:  0
            Defect Severity:         |
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 I have made a new branch `trac1899_2`. It reimplements the bug fix:

 * A check constraint is added on `nsec3` table to ensure that only one
 NSEC3 RR exists per-owner, per-zone.
 * The UNION clause is split into two individual clauses per table.
 * Unnecessary columns are no longer selected.
 * The `ORDER BY` for `nsec3` table results is gone (as there's only one
 result per-owner and they can be in any order when iterating a zone).
 * A testcase was updated to check that records in the `nsec3` table were
 actually being returned.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1899#comment:15>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development