db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Thalamati <suresh.thalam...@gmail.com>
Subject Re: [PATCH] increasinng the possible log file id's from 2^22 -1 to 2^33 -1 (derby-101)
Date Thu, 19 May 2005 23:45:27 GMT
I just realized , this patch actaully break's hard upgrade also, if  log 
needs to be replayed.
Becuase I extract the log file number and log file postion from the 
instant that is on disk ,
differently after my change.

If  any one else on the list  is testing  upgrade is hitting this 
problem, please let me know.
I can post a patch to backout the portion that cause upgrade issues.

Mike Matrigali wrote:

>I am looking at committing this.  The changes look good to me, but I
>believe there are upgrade issues to handle.
>For a hard upgrade either new or old databases are fine.
>For a soft upgrade I think there is a problem if the db generates enough
>log files to start using the new bits, and then the software is reverted
>to before the fix.
>Seems like using the bits needs to be somehow only enabled for hard
>upgrade.  It would be best if it was controlled just by hard upgrade,
>but if that is not possible then just doing it for databases created
>since this version would also work - but still leave problems with old
>hard upgraded databases.
>I have reviewed the code and am running tests.  I plan on committing
>this part of the fix and let you address upgrade issues with a follow on
>Suresh Thalamati wrote:

View raw message