Re: The consequenses of interrupted vacuum

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: The consequenses of interrupted vacuum
Date: 2016-10-27 19:53:46
Message-ID: 20161027155346.52eca8c5cf6c285adaeeaeb7@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 27 Oct 2016 10:44:03 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> > I'm asking for cases of large tables where autovacuum frequently gets
> > interrupted. I'm trying to understand if the partial runs are at least
> > making _some_ progress so the next vacuum has less to do, or if this is
> > a serious problem that I need to fiddle with tuning to fix.
>
> It's probably making some progress but not much. You need to fix that.

Thanks for the feedback. The good news is that grepping through recent logs,
I'm not seeing the problem any more. So I must have just noticed it on a
particularly problematic day last time I looked.

--
Bill Moran <wmoran(at)potentialtech(dot)com>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2016-10-27 23:57:54 Save query results to new table
Previous Message Hans Schou 2016-10-27 19:29:17 restore/pg_dump only one id, with relation (cascade)