Re: GUC for cleanup indexes threshold.
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, "Ideriha, Takeshi" <ideriha.takeshi@jp.fujitsu.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Date: 2017-02-24T03:19:02Z
Lists: pgsql-hackers
On Thu, Feb 23, 2017 at 5:15 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > On Wed, Feb 22, 2017 at 12:01 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > >> I understand that there could be some delay in reclaiming dead pages >> but do you think it is such a big deal that we completely scan the >> index for such cases or even try to change the metapage format? > > IIUC, I think that we need to have the number of half-dead pages in meta page. > Don't you think we need to consider backward compatibility if we want to do that? > Isn't it a problem that the freespace map of btree index is not > vacuumed if all vacuums skip the second pass? > AFAIU, you want to skip only when there is no dead tuple removal, if so what is the need to update freespace map of btree index? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
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