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 "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/02/27 00:33:24 UTC
[jira] Commented: (DERBY-1039) Database creation should fail if
specified log device path already exists
[ http://issues.apache.org/jira/browse/DERBY-1039?page=comments#action_12367869 ]
Daniel John Debrunner commented on DERBY-1039:
----------------------------------------------
The proposed solution from the summary seems too extreme and could break existing applications. If the logDevice path already exists but is empty then there is no problem, I know I've set up scripts like this in the past. Should the checks be limited to situations that cause problems, namely as described in the description, the directory alredy contains old log files?
> Database creation should fail if specified log device path already exists
> -------------------------------------------------------------------------
>
> Key: DERBY-1039
> URL: http://issues.apache.org/jira/browse/DERBY-1039
> Project: Derby
> Type: Improvement
> Components: Newcomer, Store
> Versions: 10.2.0.0, 10.1.2.1, 10.3.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: logd.sql
>
> If a database is created with logDevice pointing to a directory
> containing old log files, one might experience errors during recovery.
> ERROR XSDB4: Page Page(0,Container(0, 768)) is at version 2,657, the
> log file contains change version 2,715, either there are log records
> of this page missing, or this page did not get written out to disk
> properly.
> To avoid this problem, database creation should fail if logDevice is
> pointing to an existing directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-1039) Database creation should fail
if specified log device path already exists
Posted by Suresh Thalamati <su...@gmail.com>.
I am ok with checking for any empty log directory. But I am curious
why would log dir be empty if it was used before unless user is
explicitly deleting the files, in which cases he/she can delete the
"log" dir too. My understanding is Derby creates "log" directory
under the user specified path. logDevice can be specified only on
creation, What is the backward compatability scenario we are trying to
solve, am I missing something.
Thanks
-suresht
Daniel John Debrunner (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1039?page=comments#action_12367869 ]
>
> Daniel John Debrunner commented on DERBY-1039:
> ----------------------------------------------
>
> The proposed solution from the summary seems too extreme and could break existing applications.
If the logDevice path already exists but is empty then there is no
problem,
I know I've set up scripts like this in the past. Should the checks be
limited to situations that cause problems,
namely as described in the description,
the directory alredy contains old log files?
>
>
>>