Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
Mahendra Singh Thalor <mahi6run@gmail.com>
From: Mahendra Singh Thalor <mahi6run@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: tushar <tushar.ahuja@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-04-08T14:24:49Z
Lists: pgsql-hackers
On Wed, 8 Apr 2020 at 17:59, Robert Haas <robertmhaas@gmail.com> wrote: > > 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. > I think, Tushar point is that either we should allow both vacuum(parallel 0, full 1) and vacuum(parallel 1, full 0) or in the both cases, we should through error. -- Thanks and Regards Mahendra Singh Thalor EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix the usage of parallel and full options of vacuum command.
- 24d2d38b1eb8 13.0 landed
-
pg_restore -jN does not equate "multiple jobs", so partly revert the
- 14a4f6f3748d 8.4.0 cited