Re: The consequenses of interrupted vacuum - Mailing list pgsql-general

From Bill Moran
Subject Re: The consequenses of interrupted vacuum
Date
Msg-id 20161027155346.52eca8c5cf6c285adaeeaeb7@potentialtech.com
Whole thread Raw
In response to Re: The consequenses of interrupted vacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, 27 Oct 2016 10:44:03 -0400
Tom Lane <tgl@sss.pgh.pa.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@potentialtech.com>


pgsql-general by date:

Previous
From: Hans Schou
Date:
Subject: restore/pg_dump only one id, with relation (cascade)
Next
From: jaroet
Date:
Subject: slow performance of array_agg after upgrade from 9.2 to 9.5