db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5785) investigate improving identity column performance by reusing nested transaction
Date Fri, 25 May 2012 16:44:22 GMT
Mike Matrigali created DERBY-5785:
-------------------------------------

             Summary: investigate improving identity column performance by reusing nested
transaction
                 Key: DERBY-5785
                 URL: https://issues.apache.org/jira/browse/DERBY-5785
             Project: Derby
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 10.8.2.2
            Reporter: Mike Matrigali
            Priority: Minor


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message