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
>
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:
> > Justin Pryzby wrote:
> >
> > > Core was generated by `postgres: autovacuum worker process gtt
> > >'.
> > > Program terminated with signal 11, Segmen
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,
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=, stats=0x0) at mvdistinct.c:103
> 103
Justin Pryzby wrote:
> After adding extended/MV stats to a few of our tables a few days ago, it looks
> like I wasn't been paying attention and this first crashed 2 nights ago. Why
> at 1am? not sure. I have an "reindex" job which runs at 1am, and an
> vacuum/analyze job which runs at 2am, but I
After adding extended/MV stats to a few of our tables a few days ago, it looks
like I wasn't been paying attention and this first crashed 2 nights ago. Why
at 1am? not sure. I have an "reindex" job which runs at 1am, and an
vacuum/analyze job which runs at 2am, but I don't use cron to change
aut
