[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689154#action_12689154
]
Knut Magne Solem commented on DERBY-646:
----------------------------------------
You need the log for undo, but for committed transactions I can't see why you
need to keep the log records for a non-durable in-memory database. It could be
hard to do this because you are doing in-memory stuff on this level. I tried to
just discard writing log records to virtualFiles, but rollback failed because
it was flushing the log and reading undo records from the storage. So we need
to keep some log in virtualFiles to get undo working :)
> In-memory backend storage support
> ---------------------------------
>
> Key: DERBY-646
> URL: https://issues.apache.org/jira/browse/DERBY-646
> Project: Derby
> Issue Type: New Feature
> Components: Store
> Affects Versions: 10.5.0.0
> Environment: All
> Reporter: Stephen Fitch
> Assignee: Kristian Waagan
> Attachments: derby-646-1a-raw-compiles.diff,
> derby-646-1a-raw-compiles.stat, derby-646-20090222.diff,
> derby-646-20090222.stat, derby-646-2a-vfmem_first_rev.diff,
> derby-646-2a-vfmem_first_rev.stat, derby-646-2b-vfmem_first_rev.diff,
> derby-646-3a-jmx_experiment.diff, derby-646-performance_comparison_1a.txt,
> svn.diff
>
>
> To allow creation and modification of databases in-memory without requiring
> disk access or space to store the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
