Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iL7jE-00089P-Fy for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Oct 2019 15:30:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iL7jB-0002KA-Ve for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Oct 2019 15:30:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iL7jB-0002Jn-Fg for pgsql-hackers@lists.postgresql.org; Thu, 17 Oct 2019 15:30:13 +0000 Received: from mail-il1-x141.google.com ([2607:f8b0:4864:20::141]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iL7j8-0007Nz-CN for pgsql-hackers@lists.postgresql.org; Thu, 17 Oct 2019 15:30:12 +0000 Received: by mail-il1-x141.google.com with SMTP id c12so2470786ilm.1 for ; Thu, 17 Oct 2019 08:30:10 -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=2gEXzA3OuuoixLMkrglRgDJkHwwCH1VEUhC0OxHq7+M=; b=dQqPCrD7p7gRV1CN93xHWOzjuM9LjTkY6UTQVwhdoJCyciWb1qJyvbvIY+bd4OO0Sk K2uiLhVYMIvNsZUHwJcdO5VRXMkeZj5xZdR+/TfKYxIOAiva5fJ7j0UNRN7msxUObdbw U9xO6alle4uI/wJTkWDm3t3eHnl4VonRV3876OEZabKM8a0jEsvYCoq2S67RB5XIXyxx zi1gS8jNEutpIHYmWg1MtttB/RpW01yU1KeNXWqc3FtHQ3jw51JNsTvubAe6HMHXwbNZ F0NToIerbEsxH8U9WonFTAe7P07u2gyOopm3njlybMLYXI4E+puAMUN6fQiO/iEzrKiY Bc9w== 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=2gEXzA3OuuoixLMkrglRgDJkHwwCH1VEUhC0OxHq7+M=; b=oTp9EOkCFmTvIQykn+aFjpOfsjbu9Q3kmW5I2U3gLIEreqsKhUM6Pyi4RePuf29tNw ozWUQkpsg64KykUGkqpPG6paira58LZi3XpoGLcW9sA36h5Y+IQFNbHAzeF658M/R7LS Zw6e+Dh5lzmnnKq6fX+9brTYmmDapIK8iTLkp0DlqIHv2IECsiEjnck4nED3xxExtQd2 ofCJOifmr7hg5rxbRP1kPpiUKbhR4rGrfxhrix7IZzTvZnAkpnTUCXjti1NB8YZ5Lgc/ b8ovkGt/qoD0+69TnMwf+lW9Ks2w3XyeFT8tnAzwNDPk+DwqYF9OajVlw3zLD/Am1s5R gtHA== X-Gm-Message-State: APjAAAUJuOSO2L0zZ75RdCGEqjH9bUFDKoxMjbaJPUJd648uWRIer8Yd CGQCtA7/dFhpTsPIvqRRZdsuUg== X-Google-Smtp-Source: APXvYqyprVmRrcwRvKgp2ukq+XL3e8Tlyjhl9VYQ1pX/Pb/nPT8yv2x5ystCYnppqKAetKmNp83Zcw== X-Received: by 2002:a92:1d5c:: with SMTP id d89mr4337539ild.185.1571326208806; Thu, 17 Oct 2019 08:30:08 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id h75sm1054682ilf.67.2019.10.17.08.30.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Oct 2019 08:30:07 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 81D1A800CC6; Thu, 17 Oct 2019 10:30:06 -0500 (CDT) Date: Thu, 17 Oct 2019 10:30:06 -0500 From: Justin Pryzby To: Tom Lane Cc: Stephen Frost , imai.yoshikazu@fujitsu.com, Euler Taveira , Andrew Gierth , PostgreSQL Hackers Subject: Re: v12 and pg_restore -f- Message-ID: <20191017153006.GA3599@telsasoft.com> References: <20191006190839.GE18030@telsasoft.com> <28770.1570394593@sss.pgh.pa.us> <875zl11tla.fsf@news-spur.riddles.org.uk> <30069.1570396524@sss.pgh.pa.us> <20191008180840.GQ6962@tamriel.snowman.net> <20191009124505.GT6962@tamriel.snowman.net> <20191016172148.GH6962@tamriel.snowman.net> <19891.1571307850@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19891.1571307850@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Oct 17, 2019 at 12:24:10PM +0200, Tom Lane wrote: > Alternatively, we could revoke the requirement to use "-f -" in 12, > and wait a couple releases before enforcing it. The fundamental > problem here is that we tried to go from "-f - doesn't work" to > "you must use -f -" with no grace period where "-f - is optional". > In hindsight that was a bad idea. I'm going to make an argument in favour of keeping the enforcement of -f- in v12. If there's no enforcement, I don't know if many people would naturally start to use -f-, which means that tools which need to work across a wide range of (minor) versions may never confront this until it's enforced in v14/v15, at which point we probably end up revisiting the whole thing again. Failing pg_restore forces people to confront the new/different behavior. If we defer failing for 2 years, it probably just means it'll be an issue again 2 years from now. However, it's still an issue if (old) back branches (like 11.5) don't support -f-, and I think the differing behavior should be called out in the v12 release notes, as succinctly as possible. Also, I'm taking the opportunity to correct myself, before someone else does: On Wed, Oct 16, 2019 at 02:28:40PM -0500, Justin Pryzby wrote: > And vendors (something like pgadmin) will end up "having to" write to a file > to be portable, or else check the full version, not just the major version. I take back that part .. before v12, they'd get stdout by not specifying -f, and since 12.0 they'd get stdout with -f-. No need to check the minor version, since the "need to" specify -f- wouldn't be backpatched, of course. Justin