Re: parallel vacuum comments

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(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-30 06:00:28
Message-ID: CAA4eK1JHrHuFGD4ZL13vx-_g+pwQ9Pq_fOxqwjuecyX0Kc+S9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 30, 2021 at 11:03 AM houzj(dot)fnst(at)fujitsu(dot)com
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Mon, Nov 29, 2021 11:38 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> >
>
> 2)
> + /* Reinitialize the parallel context to relaunch parallel workers */
> + if (!pvs->first_time)
>
> It seems the ParallelVacuumState::first_time was not initialized before ?
>

Yeah, I also notice this while looking at the patch.

One more thing it seems the patch has removed even the existing error
callback from parallel_vacuum_main. I suggested that we can enhance or
add a new one if required in a separate patch but let's keep the
current one as it is.

Can we think of splitting the patch in the following manner: (a) the
patch to get rid of bitmap to represent whether particular index
supports parallel vacuum and rename of functions (b) any other stuff
to improve the current implementation, (c) move the parallel vacuum
related code to a separate file?

I think if we can split the patch, it will be easier to review and
reduce the chances of introducing any bugs in this area.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-11-30 06:07:08 Re: row filtering for logical replication
Previous Message Sasasu 2021-11-30 05:55:29 Re: [PATCH] buffile: ensure start offset is aligned with BLCKSZ