| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Failed to request an autovacuum work-item in silence |
| Date: | 2018-03-15 10:35:03 |
| Message-ID: | 20180315103503.fenqmxxxjampd3t4@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Masahiko Sawada wrote:
> On Thu, Mar 15, 2018 at 12:06 AM, Alvaro Herrera
> <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2018-03-15 10:55:44 | Passing estate to assign_simple_var() |
| Previous Message | Arthur Zakirov | 2018-03-15 10:33:51 | Re: pg_get_functiondef forgets about most GUC_LIST_INPUT GUCs |