On Fri, May 1, 2026 at 12:58 PM Andres Freund <[email protected]> wrote: > Well, right now the regress_log* files that involve combining backups are so > long that it's hard to find the actual stuff that's happening - and it's worse > with the test Melanie is proposing because it runs a few iterations of > combining backups. So I think it's not universal that you'd want it.
Fair enough. > > Another possible approach could be to direct the output to a temporary > > file. At the end of the test run, if no tests failed, remove the file. > > If there were any failures, copy that file's contents into the log. > > I think that's probably the better direction. I'd not even include it > directly into regress_log, just put it alongside it, like we have the server > logs etc. Oh, yeah, OK, as long as CI will capture it, that WFM. -- Robert Haas EDB: http://www.enterprisedb.com
