Re: Failed to request an autovacuum work-item in silence
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Ildar Musin <i.musin@postgrespro.ru>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-03-16T00:43:23Z
Lists: pgsql-hackers
On Thu, Mar 15, 2018 at 7:35 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > Masahiko Sawada wrote: >> On Thu, Mar 15, 2018 at 12:06 AM, Alvaro Herrera >> <alvherre@alvh.no-ip.org> wrote: > >> > Now I'm wondering what will we tell users to do if they get this message >> > too frequently. Neither of the obvious options (1. changing the index's >> > pages_per_range to a larger value; 2. making autovacuum more frequent >> > somehow) seem terribly useful. >> >> Or telling users to call brin_summarize_range() manually? > > Yeah, they can do that to fix the situation with each unsummarized > range, but that won't silence the log message ... oh! Unless you call it > to summarize the range ahead of time -- I think that should fix it. Is > that what you were thinking? > Yes. Or with this situation since the multiple work-item for the same index but different block number might be listed the calling brin_summarize_new_values() manually would rather fix the situation more properly? Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
Commits
-
Log when a BRIN autosummarization request fails
- eadcb7a2377a 10.4 landed
- 484a4a08abe3 11.0 landed