| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Илья Чердаков <i(dot)cherdakov(dot)pg(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Environment variable to disable diffs file output |
| Date: | 2026-04-06 09:47:02 |
| Message-ID: | CAGECzQTgidHEanmHbcihiEfZ3D2hinqrR57n6YH3n94+k1z4GA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 6 Apr 2026 at 09:56, Илья Чердаков <i(dot)cherdakov(dot)pg(at)gmail(dot)com> 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).
I'm fine with adding the abilitity to configure what pg_regress should
print, but it's unclear to me what's special about the diff output
compared to all the other output? i.e. what is the output you would
actually like to see for your use case? Piping everything to /dev/null
would silence all output except for the exit code, but I guess you
want some output. i.e. what do you do with the output that you get? Do
you only want to know which tests failed? If so, do you care about
which tests are passing?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2026-04-06 09:58:39 | Re: Stack-based tracking of per-node WAL/buffer usage |
| Previous Message | Amit Langote | 2026-04-06 09:45:05 | Re: Eliminating SPI / SQL from some RI triggers - take 3 |