Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9kfd-001iC3-11 for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:11:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9kfb-0092IS-2S for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:11:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9kfb-0092IK-1Z for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:11:15 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w9kfZ-00000000uQU-2hp5 for pgsql-hackers@postgresql.org; Mon, 06 Apr 2026 14:11:15 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 791D35860CA for ; Mon, 06 Apr 2026 16:11:13 +0200 (CEST) Received: from s934.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 604895863AE; Mon, 06 Apr 2026 16:11:13 +0200 (CEST) Received: from localhost (unknown [172.22.191.6]) by s934.loopia.se (Postfix) with ESMTP id 572207CE94E; Mon, 06 Apr 2026 16:11:13 +0200 (CEST) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s470.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s980.loopia.se ([172.22.191.6]) by localhost (s470.loopia.se [172.22.190.34]) (amavis, port 10024) with UTF8LMTP id Pv8rZsmYRlWE; Mon, 6 Apr 2026 16:11:13 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id D22602201514; Mon, 06 Apr 2026 16:11:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1775484672; bh=m85Tgi9razfvaAnASn/Oeaqi23teIWHxecAzBftTghk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=EHNsW6alStrvgnVIYKeH+eIC063BgCsQ+b7lsZusz1+e435P1g50xW1pdGY6vfmJJ tEu3GlJcU0/XveQvAVFhNZf0SwQ8X6D4QXCr3vUvW4ctV3hl/Sr/5ZjHDuhbqKlKRC w52Rc6YXRD7ozOYQcD/W21FoTvrdy5mZUzNuIKzuzQcSokMER2g4zhSr6TkopYmZoO 4+TzIXx9r3LvTNyFu9u6Cjz1/9iniIVs/pm5gKy38Tgjjva1GYTj41VawNpyGbL4RO ph5y2DMwDWbH0R31lDR8h4ZlzlH+JMLdGd6VfmVAEwd+0hEYCQ2+m4QWHyAVZWWXj8 caQLf/TToftfA== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: Environment variable to disable diffs file output From: Daniel Gustafsson In-Reply-To: Date: Mon, 6 Apr 2026 16:11:02 +0200 Cc: PostgreSQL Hackers , postgres@jeltef.nl Content-Transfer-Encoding: quoted-printable Message-Id: References: To: =?utf-8?B?0JjQu9GM0Y8g0KfQtdGA0LTQsNC60L7Qsg==?= X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 6 Apr 2026, at 09:55, =D0=98=D0=BB=D1=8C=D1=8F =D0=A7=D0=B5=D1=80=D0=B4= =D0=B0=D0=BA=D0=BE=D0=B2 wrote: > I'd like to add a environment variable to the patch to > disable diff output. Sometimes you have to be creative > with exploratory testing, modifying test files, etc., > and multiple diff outputs can become a nuisance. This > doesn't change the default behavior, but it does give > you control over diff output in tests for specific > scenarios where a large number of failures are expected > (mass runs or exploratory testing with changing tests). >=20 > The env usage and implementation are somewhat similar > to PG_REGRESS_DIFF_OPTS > PG_REGRESS_DISABLE_DIFFS_OUTPUT=3D1 make check -s. >=20 > For now, I suggest to simply disabling it, but I'm also > considering passing the number of lines to output via env > or via flag pg_regress instead of completely disabling it. > Something like > PG_REGRESS_DIFFS_NUMBER_LINES_OUTPUT=3D20 make check > and then when an error occurs, 20 lines will be output > instead of the default 80. Setting it to 0 disables > diffs output. I'm not sure I entirely understand the problem. If you expect lots of failures, but also don't want to see the test failures, what is the use = of running the tests? Why not run the subset you actually care about and = expand that set as testing fixes bugs/issues? -- Daniel Gustafsson