Postgres Pro
Downloads
Home   >   mailing lists

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

From tushar
Subject Vacuum o/p with (full 1, parallel 0) option throwing an error
Date
Msg-id 58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com
Whole thread Raw
Responses Re: Vacuum o/p with (full 1, parallel 0) option throwing an error  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
Hi,

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.

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: adding partitioned tables to publications
Next
From: Michail Nikolaev
Date:
Subject: Re: Thoughts on "killed tuples" index hint bits support on standby