Horton

Re: Vacuum o/p with (full 1, parallel 0) option throwing an error

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Mahendra Singh Thalor <mahi6run@gmail.com>
Cc: tushar <tushar.ahuja@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-04-08T15:57:08Z
Lists: pgsql-hackers 
On Wed, Apr 8, 2020 at 10:25 AM Mahendra Singh Thalor
<mahi6run@gmail.com> wrote:
> 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.

Oh, yeah, good point. Somebody must not've been careful enough with
the options-checking code.

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

Commits

  1. Fix the usage of parallel and full options of vacuum command.

  2. pg_restore -jN does not equate "multiple jobs", so partly revert the