Re: [HACKERS] GUC for cleanup indexes threshold.
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: sawada.mshk@gmail.com
Cc: teodor@sigaev.ru, 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-06T08:33:08Z
Lists: pgsql-hackers
At Fri, 6 Apr 2018 10:52:58 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in <CAD21AoCYWuKu4yvTLE1Hgv2SsJRnBjYweTztTkBABUykXonb1w@mail.gmail.com> > On Thu, Apr 5, 2018 at 7:23 PM, Teodor Sigaev <teodor@sigaev.ru> wrote: > > Thanks to everyone, fixes are pushed except nodeMerge.c, I don't wish to > > increase entropy around MERGE patch :) No problem. Thanks! > Thank you! regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Fix upper limit for vacuum_cleanup_index_scale_factor
- 4d54543efa5e 11.0 landed
-
Increase upper limit for vacuum_cleanup_index_scale_factor
- 6ca33a885bf8 11.0 landed
-
Fixes for vacuum_cleanup_index_scale_factor GUC option
- 9a994e37e08d 11.0 landed
-
Skip full index scan during cleanup of B-tree indexes when possible
- 857f9c36cda5 11.0 landed