[
https://issues.apache.org/jira/browse/DERBY-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali resolved DERBY-806.
----------------------------------
Resolution: Fixed
> One each deleted or updated from a heap row a new RowPosition object is
> created.
> --------------------------------------------------------------------------------
>
> Key: DERBY-806
> URL: https://issues.apache.org/jira/browse/DERBY-806
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> See the new RowPosition in GenericConglomerateController.delete and replace.
> The fetch methods also have new RowPosition calls but in general these calls
> are not made for scans.
> Can a single RowPosition object be re-used across the life of the query?
> In general Derby should try to avoid creating objects per row in any
> statement as the gc overhead when operating on a large number of rows can be
> high.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
