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] Resolved: (DERBY-150) Disable transaction logging
Date Tue, 29 Jun 2010 21:26:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali resolved DERBY-150.

    Resolution: Won't Fix

Given the Derby architecture it is unlikely a no logging option would be provided.

DERBY-218 provides better performance if durable transactions are not necessary.
DERBY-646 provides an in-memory version which also provide the performance this request is
getting at.

> Disable transaction logging
> ---------------------------
>                 Key: DERBY-150
>                 URL: https://issues.apache.org/jira/browse/DERBY-150
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>         Environment: all
>            Reporter: Barnet Wagman
> As a means of improving performance, I would like to be able to disable logging completely.
> I use Derby in applications thatnever use rollback and I suspect that quite a lot of
time is going to logging.
> Thanks

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message