farrokhi/pg_repack
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed docs reST formatting

Browse Source 
In Japanese too! ツ
This commit is contained in:
Daniele Varrazzo 2017-03-23 18:06:45 +00:00
parent 9bef0d4fa7
commit 81cca1836b
2 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/pg_repack.rst
View File

@ -382,21 +382,19 @@ WARNING: the table "tbl" already has a trigger called repack_trigger
You can remove all the temporary objects by dropping and re-creating the You can remove all the temporary objects by dropping and re-creating the
extension: see the installation_ section for the details. extension: see the installation_ section for the details.
ERROR: Another pg_repack command may be running on the table. Please try again ERROR: Another pg_repack command may be running on the table. Please try again later.
later. There is a chance of deadlock when two concurrent pg_repack commands are
run on the same table. So, try to run the command after some time.
There is a chance of deadlock when two concurrent pg_repack commands are run
on the same table. So, try to run the command after some time.
WARNING: Cannot create index "schema"."index_xxxxx", already exists WARNING: Cannot create index "schema"."index_xxxxx", already exists
DETAIL: An invalid index may have been left behind by a previous pg_repack on DETAIL: An invalid index may have been left behind by a previous pg_repack
the table which was interrupted. Please use DROP INDEX "schema"."index_xxxxx" on the table which was interrupted. Please use DROP INDEX
to remove this index and try again. "schema"."index_xxxxx" to remove this index and try again.
A temporary index apparently created by pg_repack has been left behind, and A temporary index apparently created by pg_repack has been left behind, and
we do not want to risk dropping this index ourselves. If the index was in we do not want to risk dropping this index ourselves. If the index was in
fact created by an old pg_repack job which didn't get cleaned up, you fact created by an old pg_repack job which didn't get cleaned up, you
should just use DROP INDEX and try the repack command again. should just use DROP INDEX and try the repack command again.
Restrictions Restrictions

5
doc/pg_repack_jp.rst
View File

@ -363,14 +363,15 @@ OPTIONには以下のものが指定できます。
The default is 60 seconds. The default is 60 seconds.
``-T SECS``, ``--wait-timeout=SECS`` ``-T SECS``, ``--wait-timeout=SECS``
pg_repackは再編成の完了直前に排他ロックを利用します。このオプションは、このロック取得時に何秒間pg_repackが取得を待機するかを指定します。指定した時間経ってもロックが取得できないかつ、`no-kill-backend`オプションが指定されていない場合、pg_repackは競合するクエリを強制的にキャンセルさせます。PostgreSQL 8.4以上のバージョンを利用している場合、指定した時間の2倍以上経ってもロックが取得できない場合、pg_repackは競合するクエリを実行しているPostgreSQLバックエンドプロセスをpg_terminate_backend()関数により強制的に停止させます。このオプションのデフォルトは60秒です。 pg_repackは再編成の完了直前に排他ロックを利用します。このオプションは、このロック取得時に何秒間pg_repackが取得を待機するかを指定します。指定した時間経ってもロックが取得できないかつ、``no-kill-backend``\オプションが指定されていない場合、pg_repackは競合するクエリを強制的にキャンセルさせます。PostgreSQL 8.4以上のバージョンを利用している場合、指定した時間の2倍以上経ってもロックが取得できない場合、pg_repackは競合するクエリを実行しているPostgreSQLバックエンドプロセスをpg_terminate_backend()関数により強制的に停止させます。このオプションのデフォルトは60秒です。
.. ``-D``, ``--no-kill-backend`` .. ``-D``, ``--no-kill-backend``
Skip to repack table if the lock cannot be taken for duration specified Skip to repack table if the lock cannot be taken for duration specified
``--wait-timeout``, instead of cancelling conflicting queries. The default ``--wait-timeout``, instead of cancelling conflicting queries. The default
is false. is false.
``-D``, ``--no-kill-backend`` ``-D``, ``--no-kill-backend``
``--wait-timeout``オプションで指定された時間が経過してもロックが取得できない場合、競合するクエリをキャンセルする代わりに対象テーブルの再編成をスキップします。 ``--wait-timeout``\オプションで指定された時間が経過してもロックが取得できない場合、競合するクエリをキャンセルする代わりに対象テーブルの再編成をスキップします。
.. ``-Z``, ``--no-analyze`` .. ``-Z``, ``--no-analyze``
Disable ANALYZE after a full-table reorganization. If not specified, run Disable ANALYZE after a full-table reorganization. If not specified, run