Re: [HACKERS] GUC for cleanup indexes threshold.

Teodor Sigaev <teodor@sigaev.ru>

From: Teodor Sigaev <teodor@sigaev.ru>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, sawada.mshk@gmail.com
Cc: a.korotkov@postgrespro.ru, simon@2ndquadrant.com, y.sokolov@postgrespro.ru, pg@bowt.ie, andres@anarazel.de, robertmhaas@gmail.com, david@pgmasters.net, amit.kapila16@gmail.com, ideriha.takeshi@jp.fujitsu.com, pgsql-hackers@postgresql.org, kuntalghosh.2007@gmail.com, pgsql-hackers-owner@postgresql.org
Date: 2018-04-05T10:23:17Z
Lists: pgsql-hackers
Thanks to everyone, fixes are pushed except nodeMerge.c, I don't wish to 
increase entropy around MERGE patch :)

Kyotaro HORIGUCHI wrote:
> Hello.
> 
> The commit leaves three warnings for
> -Wunused-but-set-variable. Two of them are not assertion-only but
> really not used at all.
> 
> I also found that nodeMerge.c has one such variable.
> 
> regards.
> 
> At Thu, 5 Apr 2018 15:43:55 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in <CAD21AoAtYzXeuhPqGw89KxqcJWpSKxWRNkYzyJxAqJHZham==Q@mail.gmail.com>
>> On Thu, Apr 5, 2018 at 2:40 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>>> On Thu, Apr 5, 2018 at 1:30 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:
>>>> Thanks for everyone, pushed with minor editorization
>>>>
>>>
>>> Thank you for committing!
>>> I found a typo in nbtpage.c and attached a patch fixes it.
>>>
>>
>> I also found an incorrect documentation in create_index.sgml as follows.
>>
>>       <term><literal>vacuum_cleanup_index_scale_factor</literal></term>
>>       <listitem>
>>       <para>
>>        Per-table value for <xref
>> linkend="guc-vacuum-cleanup-index-scale-factor"/>.
>>       </para>
>>       </listitem>
>>      </varlistentry>
>>
>> I think it should be "Per-index". Attached a patch for fixing it. And
>> sorry for missing it at review.
>>
>> Regards,
> 

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/


Commits

  1. Fix upper limit for vacuum_cleanup_index_scale_factor

  2. Increase upper limit for vacuum_cleanup_index_scale_factor

  3. Fixes for vacuum_cleanup_index_scale_factor GUC option

  4. Skip full index scan during cleanup of B-tree indexes when possible