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

From Masahiko Sawada
Subject Re: Failed to request an autovacuum work-item in silence
Date
Msg-id CAD21AoB5AgAF8KJQgpnBDe36ZNpw0yYXW43_EJx422jrRzVLFA@mail.gmail.com
Whole thread Raw
In response to Re: Failed to request an autovacuum work-item in silence  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List 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


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Clarification needed for comment in storage/file/fd.c
Next
From: Tomas Vondra
Date:
Subject: Re: Parallel Aggregates for string_agg and array_agg