Yasuhiro Horimoto
null+****@clear*****
Thu Jan 11 11:49:44 JST 2018
Yasuhiro Horimoto 2018-01-11 11:49:44 +0900 (Thu, 11 Jan 2018) New Revision: 32c5ef955eaa6515f74336d27602dc0abb05eefa https://github.com/groonga/groonga/commit/32c5ef955eaa6515f74336d27602dc0abb05eefa Merged 7bf8f02: Merge pull request #809 from komainu8/add_document_for_force_lock_clear Message: doc grndb: add --force-lock-clear option's information Modified files: doc/locale/ja/LC_MESSAGES/reference.po doc/source/reference/executables/grndb.rst Modified: doc/locale/ja/LC_MESSAGES/reference.po (+34 -0) =================================================================== --- doc/locale/ja/LC_MESSAGES/reference.po 2018-01-11 09:34:34 +0900 (088d5709d) +++ doc/locale/ja/LC_MESSAGES/reference.po 2018-01-11 11:49:44 +0900 (3932bd2a2) @@ -16626,6 +16626,40 @@ msgstr "" "に存在するデータベースのオブジェクトファイルの情報が食い違っているときです。 " "他にデータベースを復旧する方法がないときのみ使うべきです。" +msgid "``--force-lock-clear``" +msgstr "" + +msgid "" +"It forces to clear lock of locked objects (database, table, column). You can " +"use if you want to database recover even if remain locked of database." +msgstr "" +"ロックされているオブジェクト(データベース、テーブル、カラム)のロックを強制的" +"に解除します。データベースにロックが残留していてもデータベースを復旧させたい" +"場合に使えます。" + +msgid "Here is example that specifies ``--force-lock-clear`` option::" +msgstr "以下は ``--force-lock-clear`` オプションを指定する例です。" + +msgid "check whether there are locked objects (database, table, column)" +msgstr "" +"ロックされたオブジェクト(データベース、テーブル、カラム)がないかチェックしま" +"す。" + +msgid "clear lock of locked objects (database, table, column)" +msgstr "" +"ロックされたオブジェクト(データベース、テーブル、カラム)のロックを解除しま" +"す。" + +msgid "" +"You must use this option only when necessary. Because can not the safty " +"recover database if remain locked of database. This option should be used " +"when even if you can't recover the safety database, you want to recover the " +"database and operating it." +msgstr "" +"このオプションは必要なときのみ使用します。ロックが残留しているデータベースは" +"安全に復旧できないからです。このオプションは、安全にデータベースを復旧できな" +"い場合でも、データベースを復旧して操作したい場合に使用してください。" + msgid "grnslap" msgstr "" Modified: doc/source/reference/executables/grndb.rst (+21 -0) =================================================================== --- doc/source/reference/executables/grndb.rst 2018-01-11 09:34:34 +0900 (48d856ae3) +++ doc/source/reference/executables/grndb.rst 2018-01-11 11:49:44 +0900 (1f19dce86) @@ -169,6 +169,27 @@ against truncated tables or columns to recreate database. You must use this option only when necessary. It means that you use it when there is a mismatch between database meta information and database object files which exists actually. This options should be used when there is no other way to recover database. +``--force-lock-clear`` +"""""""""""""""""""""" + +.. versionadded:: 7.1.1 + +It forces to clear lock of locked objects (database, table, column). +You can use if you want to database recover even if remain locked of database. + +Here is example that specifies ``--force-lock-clear`` option:: + + % grndb recover --force-lock-clear --log-level info --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db + +When this option is specified, ``grndb`` does the following: + +* check whether there are locked objects (database, table, column) +* clear lock of locked objects (database, table, column) + +.. note:: + + You must use this option only when necessary. Because can not the safty recover database if remain locked of database. This option should be used when even if you can't recover the safety database, you want to recover the database and operating it. + ``--log-level`` """"""""""""""" -------------- next part -------------- HTML����������������������������... URL: https://lists.osdn.me/mailman/archives/groonga-commit/attachments/20180111/aff43df8/attachment-0001.htm
