Re: parallel vacuum comments

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: parallel vacuum comments
Date: 2021-11-24 02:47:09
Message-ID: CAA4eK1LFfWLm5AOu1Dqaj2mEbYzc3wP2UR5w0KB+4zbOs3+0vA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 24, 2021 at 7:48 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Fri, Nov 19, 2021 at 11:25 AM houzj(dot)fnst(at)fujitsu(dot)com
> <houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> >
> > 3)
> >
> > + /*
> > + * Reset all index status back to invalid (while checking that we have
> > + * processed all indexes).
> > + */
> > + for (int i = 0; i < pvs->nindexes; i++)
> > + {
> > + PVIndStats *stats = &(pvs->indstats[i]);
> > +
> > + Assert(stats->status == INDVAC_STATUS_COMPLETED);
> > + stats->status = INDVAC_STATUS_INITIAL;
> > + }
> >
> > Would it be safer if we report an error if any index's status is not
> > INDVAC_STATUS_COMPLETED ?
>
> Agreed. It'd be safer since even if some indexes are vacuumed due to a
> bug vacuum errored out rather than continue it (and cause index
> corruption).
>

I think if we want to report an error in this case, we should use elog
as this is an internal error.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-11-24 03:07:03 Python 3.11 vs. Postgres
Previous Message Thomas Munro 2021-11-24 02:31:49 Warning in geqo_main.c from clang 13