Re: Why clearing the VM doesn't require registering vm buffer in wal record - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why clearing the VM doesn't require registering vm buffer in wal record
Date
Msg-id CA+TgmoZVSTTR9wa6zNV_j0A6mZvg=xm9X1pWZh7dty1_GcE+uQ@mail.gmail.com
Whole thread
In response to Re: Why clearing the VM doesn't require registering vm buffer in wal record  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, May 1, 2026 at 12:58 PM Andres Freund <andres@anarazel.de> 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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal
Next
From: Masahiko Sawada
Date:
Subject: Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization.