Re: parallel vacuum options/syntax - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: parallel vacuum options/syntax
Date
Msg-id CAA4eK1+3zMNdHYKnmGTPoCSK=QNDV=zwj=n6O2T+g+4ZV+NX7g@mail.gmail.com
Whole thread Raw
In response to Re: parallel vacuum options/syntax  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: parallel vacuum options/syntax  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Re: parallel vacuum options/syntax  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Wed, Jan 8, 2020 at 11:31 AM Masahiko Sawada
<masahiko.sawada@2ndquadrant.com> wrote:
>
> On Mon, 6 Jan 2020 at 15:27, Masahiko Sawada
> <masahiko.sawada@2ndquadrant.com> wrote:
> >
> > I just felt it's not intuitive that specifying parallel degree to 0
> > means to disable parallel vacuum. But since majority of hackers seem
> > to agree with this syntax I'm not going to insist on that any further.
> >
>
> Okay I'm going to go with enabling parallel vacuum by default and
> disabling it by specifying PARALLEL 0.
>

Sounds fine to me.  However, I have already started updating the patch
for that.  I shall post the new version today or tomorrow.  Is that
fine with you?

> For combination of VACUUM command options, although parallel vacuum is
> enabled by default and VACUUM FULL doesn't support it yet, 'VACUUM
> (FULL)' would work. On the other hand 'VACUUM (FULL, PARALLEL)' and
> 'VACUUM(FULL, PARALLEL 1)' would not work with error. And I think it
> is better if 'VACUUM (FULL, PARALLEL 0)' also work but I'd like to
> hear opinions.
>

I agree with all these points.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: parallel vacuum options/syntax
Next
From: "曾文旌(义从)"
Date:
Subject: Re: [Proposal] Global temporary tables