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:  muks
  jinmei                             |                Status:  assigned
                       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      |
-------------------------------------+-------------------------------------

Comment (by muks):

 The UNION has been split up into two SQL clauses with manual merging.

 This still is buggy code, and it has always been buggy (with the UNION
 too) because it tries to merge rname (reversed name) from the records
 table with owner column in the nsec3 table. So you have results out of
 order. There was no unit test to check if both sides of the UNION were
 being merged properly before. Such a check has been added now, but the
 problem exists.

 We'd have to fix this by adding nsec3.rowner column.

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