pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PG10.1 autovac killed building extended stats
Date: Wed, 29 Nov 2017 00:05:50 -0300
Message-ID: <20171129030550.d3pe2cmkblyj2zvx@alvherre.pgsql> (raw)
In-Reply-To: <20171127133338.GC19405@telsasoft.com>

Justin Pryzby wrote:
> On Fri, Nov 17, 2017 at 03:43:52PM -0600, Justin Pryzby wrote:
> > On Fri, Nov 17, 2017 at 01:36:00PM -0300, Alvaro Herrera wrote:

> > > If I recall things correctly, the "continue" should be executed
> > > regardless of IsAutoVacuumWorkerProcess() (only the log should be
> > > conditional on that).  I'm not sure how I arrived at the current coding,
> > > which I added in bf2a691e02d7 -- probably just fuzzy thinking.
> > 
> > Is it useful to run with that change ?
> 
> FYI: the affected server ran without crashing since Nov 18 with this change.

Many thanks for patching and verifying that it works.  I pushed the fix
now.

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




view thread (6+ messages)

Message-ID: <20171129030550.d3pe2cmkblyj2zvx@alvherre.pgsql>
Permalink:  ../20171129030550.d3pe2cmkblyj2zvx@alvherre.pgsql/
Also on:    postgresql.org/message-id/20171129030550.d3pe2cmkblyj2zvx@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@alvh.no-ip.org, pryzby@telsasoft.com
  Subject: Re: PG10.1 autovac killed building extended stats
  In-Reply-To: <20171129030550.d3pe2cmkblyj2zvx@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox