You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2009/03/20 12:08:50 UTC

[jira] Created: (DERBY-4103) Allow unlimited growth for in-memory conglomerates

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


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.


[jira] Updated: (DERBY-4103) Allow unlimited growth for in-memory conglomerates

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4103:
-----------------------------------

    Derby Info: [Patch Available]

> 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
>         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.


[jira] Closed: (DERBY-4103) Allow unlimited growth for in-memory conglomerates

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan closed DERBY-4103.
----------------------------------


> 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.1.1, 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.5.1.1, 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.


[jira] Updated: (DERBY-4103) Allow unlimited growth for in-memory conglomerates

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4103:
-----------------------------------

    Attachment: derby-4103-1a_unlimited_growth.diff

Patch 1a implements the unlimited growth functionality, and contains one additional test.

Patch ready for review.

> 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
>         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.


[jira] Resolved: (DERBY-4103) Allow unlimited growth for in-memory conglomerates

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
     [ 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.