Re: Failed to request an autovacuum work-item in silence - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Failed to request an autovacuum work-item in silence
Date
Msg-id 20180315103503.fenqmxxxjampd3t4@alvherre.pgsql
Whole thread Raw
In response to Re: Failed to request an autovacuum work-item in silence  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Failed to request an autovacuum work-item in silence  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
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?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Arthur Zakirov
Date:
Subject: Re: pg_get_functiondef forgets about most GUC_LIST_INPUT GUCs
Next
From: Ashutosh Sharma
Date:
Subject: Passing estate to assign_simple_var()