db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4103) Allow unlimited growth for in-memory conglomerates
Date Fri, 20 Mar 2009 16:56:50 GMT

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

Kristian Waagan resolved DERBY-4103.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0
                   10.5.0.0
       Derby Info:   (was: [Patch Available])

Committed patch 1a to trunk with revision 756551, and backported it to the 10.5 branch with
revision 756612.

> Allow unlimited growth for in-memory conglomerates
> --------------------------------------------------
>
>                 Key: DERBY-4103
>                 URL: https://issues.apache.org/jira/browse/DERBY-4103
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Store
>    Affects Versions: 10.5.0.0, 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.5.0.0, 10.6.0.0
>
>         Attachments: derby-4103-1a_unlimited_growth.diff
>
>
> Allow tables and indexes in a in-memory database to grow unlimited, that is until the
system runs out of memory.
> The previous implementation had hard limits in the range 256 MB to 2048 MB (depending
on page size).

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


Mime
View raw message