| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> |
| Subject: | Re: GUC for cleanup indexes threshold. |
| Date: | 2017-03-21 17:29:26 |
| Message-ID: | 1a35d53b-581b-86dd-1a49-928462c8ac94@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 3/15/17 9:50 AM, Amit Kapila wrote:
>
> What about if somebody does manual vacuum and there are no garbage
> tuples to clean, won't in that case also you want to avoid skipping
> the lazy_cleanup_index? Another option could be to skip updating the
> relfrozenxid if we have skipped the index cleanup.
This thread has been idle for six days. Please respond and/or post a
new patch by 2017-03-24 00:00 AoE (UTC-12) or this submission will be
marked "Returned with Feedback".
Thanks,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2017-03-21 17:32:58 | Re: Measuring replay lag |
| Previous Message | Masahiko Sawada | 2017-03-21 17:23:06 | Re: GUC for cleanup indexes threshold. |