Re: Vacuum o/p with (full 1, parallel 0) option throwing an error - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
Date
Msg-id CA+TgmoY6JBix-20yS=EicJVHNAH44QnYGQhyR_c15dZi02KF-w@mail.gmail.com
Whole thread Raw
In response to Vacuum o/p with (full 1, parallel 0) option throwing an error  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: Vacuum o/p with (full 1, parallel 0) option throwing an error  (Mahendra Singh Thalor <mahi6run@gmail.com>)
List pgsql-hackers
On Wed, Apr 8, 2020 at 8:22 AM tushar <tushar.ahuja@enterprisedb.com> wrote:
> I just came across this scenario  where - vaccum o/p with (full 1,
> parallel 0) option not working
>
> --working
>
> postgres=# vacuum (parallel 1, full 0 ) foo;
> VACUUM
> postgres=#
>
> --Not working
>
> postgres=# vacuum (full 1, parallel 0 ) foo;
> ERROR:  cannot specify both FULL and PARALLEL options
>
> I think it should work.

Uh, why? There's a clear error message which matches what you tried to do.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: WIP: WAL prefetch (another approach)
Next
From: legrand legrand
Date:
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)