db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5494) Same value returned by successive calls to a sequence generator flanking an unorderly shutdown.
Date Tue, 29 May 2012 19:14:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285023#comment-13285023
] 

Rick Hillegas commented on DERBY-5494:
--------------------------------------

I applied the derby-5494_3.diff patch and built insane jars. Then I re-ran the experiments
described in the 5471-performance.html report attached to DERBY-5471. I observed the following:

o The IDENTITY 10 and IDENTITY 1 tests now run at the same transaction rate on 10.8.2.2 and
the patched trunk.

o The SEQUENCE 10 and SEQUENCE 1 tests run at the same transaction rate on the trunk and the
patched trunk.

This evidence supports the following conclusions:

1) The patch restores the concurrency of identity columns seen in 10.8.2.2.

2) The patch does not affect the concurrency of sequence generators.

So I say +1 to the patch. Thanks.
                
> Same value returned by successive calls to a sequence generator flanking an unorderly
shutdown.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5494
>                 URL: https://issues.apache.org/jira/browse/DERBY-5494
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.9.1.0
>            Reporter: Rick Hillegas
>            Assignee: Mike Matrigali
>              Labels: derby_triage10_9
>         Attachments: derby-5494_3.diff, derby-5494_diff_1a.txt, derby-5494_diff_2.txt
>
>
> The following sequence of steps causes a sequence generator to return the same value
on successive NEXT VALUE FOR calls.
> 1) Bring up ij and issue the following commands:
> connect 'jdbc:derby:db;create=true';
> create sequence s;
> values next value for s; 
> 2) Control-c out of ij so that the engine comes down hard without an orderly shutdown.
> 3) Now bring up ij again and issue the following commands:
> connect 'jdbc:derby:db';
> values next value for s; 
> Thanks to Knut for finding this one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message