From: Justin Pryzby <pryzby@telsasoft.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PG10.1 autovac killed building extended stats
Date: Fri, 17 Nov 2017 15:43:52 -0600
Message-ID: <20171117214352.GE25796@telsasoft.com> (raw)
In-Reply-To: <20171117163600.d7zsm2odaizikdhs@alvherre.pgsql>
References: <20171117152714.GA25754@telsasoft.com>
<20171117163600.d7zsm2odaizikdhs@alvherre.pgsql>
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
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: pryzby@telsasoft.com, alvherre@alvh.no-ip.org
Subject: Re: PG10.1 autovac killed building extended stats
In-Reply-To: <20171117214352.GE25796@telsasoft.com>
* 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