database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Rename pending_list_cleanup_size to gin_pending_list_limit.

Browse Source 
Since this parameter is only for GIN index, it's better to
add "gin" to the parameter name for easier understanding.
This commit is contained in:
Fujii Masao
2014-11-13 12:14:48 +09:00
parent 677708032c
commit c291503b1c
13 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/config.sgml
View File

@ -5911,10 +5911,10 @@ SET XML OPTION { DOCUMENT | CONTENT };
</listitem>
</varlistentry>
<varlistentry id="guc-pending-list-cleanup-size" xreflabel="pending_list_cleanup_size">
<term><varname>pending_list_cleanup_size</varname> (<type>integer</type>)
<varlistentry id="guc-gin-pending-list-limit" xreflabel="gin_pending_list_limit">
<term><varname>gin_pending_list_limit</varname> (<type>integer</type>)
<indexterm>
<primary><varname>pending_list_cleanup_size</> configuration parameter</primary>
<primary><varname>gin_pending_list_limit</> configuration parameter</primary>
</indexterm>
</term>
<listitem>

10
doc/src/sgml/gin.sgml
View File

@ -729,7 +729,7 @@
<acronym>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
<xref linkend="guc-pending-list-cleanup-size">, the entries are moved to the
<xref linkend="guc-gin-pending-list-limit">, the entries are moved to the
main <acronym>GIN</acronym> data structure using the same bulk insert
techniques used during initial index creation. This greatly improves
<acronym>GIN</acronym> index update speed, even counting the additional
@ -812,22 +812,22 @@
</varlistentry>
<varlistentry>
<term><xref linkend="guc-pending-list-cleanup-size"></term>
<term><xref linkend="guc-gin-pending-list-limit"></term>
<listitem>
<para>
During a series of insertions into an existing <acronym>GIN</acronym>
index that has <literal>fastupdate</> enabled, the system will clean up
the pending-entry list whenever the list grows larger than
<varname>pending_list_cleanup_size</>. To avoid fluctuations in observed
<varname>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 <varname>pending_list_cleanup_size</>
can be avoided by increasing <varname>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.
</para>
<para>
<varname>pending_list_cleanup_size</> can be overridden for individual
<varname>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

4
doc/src/sgml/ref/create_index.sgml
View File

@ -371,10 +371,10 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
</variablelist>
<variablelist>
<varlistentry>
<term><literal>pending_list_cleanup_size</></term>
<term><literal>gin_pending_list_limit</></term>
<listitem>
<para>
Custom <xref linkend="guc-pending-list-cleanup-size"> parameter.
Custom <xref linkend="guc-gin-pending-list-limit"> parameter.
This value is specified in kilobytes.
</para>
</listitem>