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 1n9Fbw-0002b5-90 for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Jan 2022 00:11:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n9Fbt-0006dY-8V for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Jan 2022 00:10:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9Fbs-0006dO-Sy for pgsql-hackers@lists.postgresql.org; Mon, 17 Jan 2022 00:10:56 +0000 Received: from mail-pj1-x1036.google.com ([2607:f8b0:4864:20::1036]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n9Fbm-0004Z1-9t; Mon, 17 Jan 2022 00:10:56 +0000 Received: by mail-pj1-x1036.google.com with SMTP id hv15so18894089pjb.5; Sun, 16 Jan 2022 16:10:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Nqx7ud/c4pU3GXsh8+Fop1poRJwQWAJwdEz/LHb+79E=; b=LCJ/xONGe7y0wdBefFZvEnf7yduveylESzTkhg1Dr1T6cuscJMh5wCEkbwLG86Hw2c FeyOdp1b/ubEM1UWYQr0M2G2hGyuPdnk5OtEC9VMYO9s0g0GdTavbKrgmgd3awEi3LQS KOz+GfPE3mYv5XjR608um8pQqR3RO2UxPJns9NTdK1kns0PYbg4FNAu3VktJcPsOcsnl WS7WCKY8MPLJxbi/Sy5JkRt2MiAm4o4GacuG+jurMhr4PdYvjgrlkXfMpf5tKlgOQEX2 vXzDP1/JTCDKkt55S0kP8Krn78hQA/dN5/C9dtD4sdCKHXn5QecEnAe5W/mNWqTnSKbP sQ5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Nqx7ud/c4pU3GXsh8+Fop1poRJwQWAJwdEz/LHb+79E=; b=ry/ba9MtMNxtEzOKTkqdgyN7xicusgqY7I30fVFWzSQcQhxBEgAVwfP+BB9jagPfOZ CZOsYsUFcYKHK1Sk19nCHtNblqZBFKMxdHYvdvlQLCdCMA7AHX6OupDI0JoFSoFa0Yaa hAYDLJy7khBGDGE/cdiabaFCkm27hj+xoOtwizlKN+YYbds4Vm89Er/0uOychj+Uxv8P vj0/X5gwk+RvEn6hiVWB1SWxEs9exdyz43O5tuhryVKNxHxrRBNBpesSYfMaPKbbpKds p7kD+Y6zzTk1FAeP1u+p6XpNWBkjfx7k4qhKGbqAyDpiKWnluPltquRxaKtUF7uJGFYP qm4A== X-Gm-Message-State: AOAM530vOUCdCeSMHYVaAI5ShS2uwa54EALrJATZhTUr93wO5UThlnQ7 MkzuoiGT3n8ozCAeZFROO30= X-Google-Smtp-Source: ABdhPJzNWxdTaxqgsjuP/2ScVqbpMaZWqSZyPz806qlKumbAOUl7icsIeSQtNNLdtqez7vDghxfsVQ== X-Received: by 2002:a17:90a:7e81:: with SMTP id j1mr31674140pjl.14.1642378247624; Sun, 16 Jan 2022 16:10:47 -0800 (PST) Received: from jrouhaud (1-171-184-213.dynamic-ip.hinet.net. [1.171.184.213]) by smtp.gmail.com with ESMTPSA id y23sm12252190pfa.80.2022.01.16.16.10.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 16 Jan 2022 16:10:47 -0800 (PST) Date: Mon, 17 Jan 2022 08:10:43 +0800 From: Julien Rouhaud To: Tom Lane Cc: Justin Pryzby , pgsql-hackers@postgresql.org, Robert Haas , "David G. Johnston" , Kyotaro HORIGUCHI , Pavel Stehule Subject: Re: default to to ON_ERROR_STOP=on (Re: psql: exit status with multiple -c and -f) Message-ID: <20220117001043.hgjci4zqt3l4susa@jrouhaud> References: <20211206150856.GJ17618@telsasoft.com> <20211227161021.GO17618@telsasoft.com> <1513136.1640626267@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1513136.1640626267@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Mon, Dec 27, 2021 at 12:31:07PM -0500, Tom Lane wrote: > Justin Pryzby writes: > > I think the current behavior of the regression test SQL scripts is exactly the > > opposite of what's desirable for almost all other scripts. The attached makes > > ON_ERROR_STOP the default, and runs the regression tests with ON_ERROR_STOP=0. > > > Is it viable to consider changing this ? > > I don't think so. The number of scripts you will break is far greater > than the number whose behavior will be improved, because people who > wanted this behavior will already be selecting it. Maybe this wasn't > the greatest choice of default, but it's about twenty years too late > to change it. > > I'd also note that I see a fairly direct parallel to "set -e" in > shell scripts, which is likewise not the default. > > We could consider documentation changes to make this issue > more visible, perhaps. Not sure what would be a good place. I'm marking the CF entry as returned with feedback as it's been a few weeks without proposal for documentation change.