Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ct1s2-0001hD-9i for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Mar 2017 00:53:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ct1s1-0008Dp-MJ for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Mar 2017 00:53:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ct1qQ-0005QK-NH; Wed, 29 Mar 2017 00:52:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ct1qO-0004ZN-42; Wed, 29 Mar 2017 00:52:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v2T0q0SQ024981; Tue, 28 Mar 2017 20:52:00 -0400 From: Tom Lane To: Corey Huinker cc: Fabien COELHO , Daniel Verite , "David G. Johnston" , Greg Stark , Erik Rijkers , Robert Haas , Jim Nasby , PostgreSQL , pgsql-hackers-owner@postgresql.org Subject: Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) In-reply-to: References: <15541.1489771669@sss.pgh.pa.us> Comments: In-reply-to Corey Huinker message dated "Mon, 27 Mar 2017 15:53:18 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24979.1490748720.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 28 Mar 2017 20:52:00 -0400 Message-ID: <24980.1490748720@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Corey Huinker writes: [ 0001-psql-if-v28.patch ] Starting to look at this version, and what jumped out at me in testing is that the regression output looks like this: parallel group (12 tests): psql_if_on_error_stop dbsize async misc_functio= ns tidscan alter_operator tsrf psql alter_generic misc stats_ext sysviews alter_generic ... ok alter_operator ... ok misc ... ok psql ... ok psql_if_on_error_stop ... ok (test process exited with exit code 3) async ... ok dbsize ... ok misc_functions ... ok sysviews ... ok tsrf ... ok tidscan ... ok stats_ext ... ok Don't think we can have that. Even if pg_regress considers it a success, every hacker is going to have to learn that that's a "pass", and I don't think I want to be answering that question every week till kingdom come. I'm not really sure we need a test for this behavior. If we're sufficiently dead set on it, we could go back to the TAP-based approach, but I still doubt that this test is worth the amount of overhead that would add. regards, tom lane --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers