Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMS3m-00071T-Vf for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Apr 2020 07:57:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jMS3l-00066E-KC for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Apr 2020 07:57:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMS3l-000666-9I for pgsql-hackers@lists.postgresql.org; Thu, 09 Apr 2020 07:57:13 +0000 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jMS3e-0008L8-DL for pgsql-hackers@postgresql.org; Thu, 09 Apr 2020 07:57:11 +0000 Received: by mail-qt1-x830.google.com with SMTP id n17so2095200qtv.4 for ; Thu, 09 Apr 2020 00:57:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=q7kG+AMK2OPg/WSZmdpddnND1wyHKrNehS4Imh8vQro=; b=KCeWxpPMMfSJ22DTpGPaMkQgh5tFaHutEGFgGfCTjMfITf4yf/CgVWax3YyqxN/nL6 W/h47PTPLv9mMX83Kw/odl/rpQqV46kb6CX7IKuWbIi7FKUFBmQ1CRHyL1ji6J/swduM 88xJ6Qv85D5nMOdaUdLr+pZkgBBf92+qxvnKvgmo/k8OgXCB7BbF9r3ti7LClGC8m0w4 HHZOyZH88184p8umSrT4r7CLAfNGuyrQ1lx9hQSwZHBqjMDj9et2Zm6fAIVB6pCz+Rf6 Xoz6mG4TIx2M6ingFWfgH5ZftvsjnoFn/eH7LrKloqpe2twLP7z3b3fl0J58S1l36TZ4 Z5RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=q7kG+AMK2OPg/WSZmdpddnND1wyHKrNehS4Imh8vQro=; b=lsSylbvtwKeLFgLR/5qA1Gb3+xMx0lWaaxt9huEP3QRsJjPjnLFz8EDHGhMERpmuTJ BY2iY5d2ACGT+CfRw7WjstfbTeARqI+jt5PVzhKVVc99mBY8f1VhNw/z43TsaF3itfWM cr72/Kb31/Zea9YMwdM/I+KSrO2a6ccL1k74wGxVHvxBghWrjeJorXO6yDVrElXWqnBF Xb6WBe60NBbLG0SYaNE6GHB11FsEITc/H88lsr0aJkFh++blxoqwUEYkmCkce5T8U4rJ mGpEpOXDP/0zrv3iY60z+jmPvOHipCAPDlGtrtossaJ9b5u1FJl1TNK4JXCvrzzBEEOw DXXw== X-Gm-Message-State: AGi0PuZtDbfYnYzYVWr9xrAzxR08YIHtn/JF353dBuuAU+IMa0W7khhZ avnnU3v3tVyBJEdXATQtGKagWQ== X-Google-Smtp-Source: APiQypJzUy0KKY59wG0l9ufME5zxTPbU1WlyZ3LFg79cyU9rJSTYpT0OB5OBlcRB/QFrmJQKYDYE5Q== X-Received: by 2002:ac8:1757:: with SMTP id u23mr11073513qtk.138.1586419025227; Thu, 09 Apr 2020 00:57:05 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id x68sm21106422qka.129.2020.04.09.00.57.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2020 00:57:04 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 9AAF1800A33; Thu, 9 Apr 2020 02:57:02 -0500 (CDT) Date: Thu, 9 Apr 2020 02:57:02 -0500 From: Justin Pryzby To: Amit Kapila Cc: Masahiko Sawada , Mahendra Singh Thalor , Robert Haas , tushar , pgsql-hackers@postgresql.org Subject: Re: Vacuum o/p with (full 1, parallel 0) option throwing an error Message-ID: <20200409075702.GM2228@telsasoft.com> References: <58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com> <20200408164154.GD2228@telsasoft.com> <20200408183854.GG2228@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Apr 09, 2020 at 12:31:55PM +0530, Amit Kapila wrote: > Sure, we can change that, but isn't the existing example of similar > message "cannot specify both PARSER and COPY options" occurs when > both the options have valid values? If so, we can use a similar > principle here, no? A better comparison is with this one: src/bin/pg_dump/pg_restore.c: pg_log_error("cannot specify both --single-transaction and multiple jobs"); but it doesn't say just: "..specify both --single and --jobs", which would be wrong in the same way, and which we already dealt with some time ago: commit 14a4f6f3748df4ff63bb2d2d01146b2b98df20ef Author: Alvaro Herrera Date: Tue Apr 14 00:06:35 2009 +0000 pg_restore -jN does not equate "multiple jobs", so partly revert the previous patch. Per note from Tom. -- Justin