From c291503b1c8250c7ba6ca900b7ba2f85a64b1eb6 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Thu, 13 Nov 2014 12:14:48 +0900 Subject: Rename pending_list_cleanup_size to gin_pending_list_limit. Since this parameter is only for GIN index, it's better to add "gin" to the parameter name for easier understanding. --- doc/src/sgml/config.sgml | 6 +++--- doc/src/sgml/gin.sgml | 10 +++++----- doc/src/sgml/ref/create_index.sgml | 4 ++-- 3 files changed, 10 insertions(+), 10 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 6bfb7bbc112..ab8c2637d75 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -5911,10 +5911,10 @@ SET XML OPTION { DOCUMENT | CONTENT }; - - pending_list_cleanup_size (integer) + + gin_pending_list_limit (integer) - pending_list_cleanup_size configuration parameter + gin_pending_list_limit configuration parameter diff --git a/doc/src/sgml/gin.sgml b/doc/src/sgml/gin.sgml index 94d2d5c19d9..262f1e452e5 100644 --- a/doc/src/sgml/gin.sgml +++ b/doc/src/sgml/gin.sgml @@ -729,7 +729,7 @@ GIN is capable of postponing much of this work by inserting new tuples into a temporary, unsorted list of pending entries. When the table is vacuumed, or if the pending list becomes larger than - , the entries are moved to the + , the entries are moved to the main GIN data structure using the same bulk insert techniques used during initial index creation. This greatly improves GIN index update speed, even counting the additional @@ -812,22 +812,22 @@ - + During a series of insertions into an existing GIN index that has fastupdate enabled, the system will clean up the pending-entry list whenever the list grows larger than - pending_list_cleanup_size. To avoid fluctuations in observed + gin_pending_list_limit. To avoid fluctuations in observed response time, it's desirable to have pending-list cleanup occur in the background (i.e., via autovacuum). Foreground cleanup operations - can be avoided by increasing pending_list_cleanup_size + can be avoided by increasing gin_pending_list_limit or making autovacuum more aggressive. However, enlarging the threshold of the cleanup operation means that if a foreground cleanup does occur, it will take even longer. - pending_list_cleanup_size can be overridden for individual + gin_pending_list_limit can be overridden for individual GIN indexes by changing storage parameters, and which allows each GIN index to have its own cleanup threshold. For example, it's possible to increase the threshold only for the GIN diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 21f7604ac08..1a23e273056 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -371,10 +371,10 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] - pending_list_cleanup_size + gin_pending_list_limit - Custom parameter. + Custom parameter. This value is specified in kilobytes. -- cgit v1.2.3