Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1732

Need way to ignore basecfg or turn off logging for wt command

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      Several times this week developers have wanted to run the wt command on a copy of a database directory. They know it is a good copy and they don't copy nor want to copy all the log files in the journal directory. Running wt runs recovery for all but the printlog command and creates new log files, etc. It would be good to have an arg, perhaps undocumented, that either tells it to ignore basecfg, or at least just forces logging off. The recent -R command was added to force recovery to run. We have the infrastructure now for turning it off, but not the mechanism for debugging and diagnostic purposes.

        Activity

        Hide
        michael.cahill Michael Cahill added a comment -

        It would be handy to have an option to wt to disable logging – that seems better to me than completely ignoring the basecfg file.

        Show
        michael.cahill Michael Cahill added a comment - It would be handy to have an option to wt to disable logging – that seems better to me than completely ignoring the basecfg file.
        Hide
        ramon.fernandez Ramon Fernandez added a comment -

        Additional ticket information from GitHub

        This ticket was referenced in the following commits:
        Show
        ramon.fernandez Ramon Fernandez added a comment - Additional ticket information from GitHub This ticket was referenced in the following commits: 6d7c061a8292021195b32260a8b41d3e92e1958f f52d17e1bc7f490654ca8b0e78072c870247255f

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since reply:
              1 year, 48 weeks, 6 days ago
              Date of 1st Reply: