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

investigate improving identity column performance by reusing nested transaction

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.8.2.2
    • Fix Version/s: None
    • Component/s: SQL
    • Urgency:
      Normal

      Description

      Currently every insert of row with an identity column creates a nested user transaction to update the
      value in syscolumns, and then destroys it. It seems like this transaction could be cached in the user
      context and then reused. I believe this is what is done for the nested read only transaction that is used
      for compiling statements.

      The change may improve performance and also lead to less objects being created/destroyed per insert.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mikem Mike Matrigali
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: