Re: PG10.1 autovac killed building extended stats - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: PG10.1 autovac killed building extended stats
Date
Msg-id 20171117214352.GE25796@telsasoft.com
Whole thread Raw
In response to Re: PG10.1 autovac killed building extended stats  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: PG10.1 autovac killed building extended stats  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Fri, Nov 17, 2017 at 01:36:00PM -0300, Alvaro Herrera wrote:
> Justin Pryzby wrote:
> 
> > Core was generated by `postgres: autovacuum worker process   gtt             '.
> > Program terminated with signal 11, Segmentation fault.
> > #0  statext_ndistinct_build (totalrows=300, numrows=300, rows=0x21df3e8, attrs=<value optimized out>, stats=0x0) at
mvdistinct.c:103
> > 103                                     item->attrs = bms_add_member(item->attrs,
> > 
> > (gdb) p stats
> > $5 = (VacAttrStats **) 0x0
> > => This is an error, no ??
> 
> Not necessarily, but then I think this previous code is busted:

> 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 ?

Justin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Treating work_mem as a shared resource (Was: Parallel Hash take II)
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Parallel Hash take II