Re: Reducing logs produced by TAP tests running pg_regress on crash

2022-07-22 Thread Michael Paquier
On Fri, Jul 22, 2022 at 01:18:34PM +1200, Thomas Munro wrote: > I wonder if we should move the noise suppression check closer to > pg_regress, so that it works also for the "main" pg_regress run, not > only the one in this new TAP test. As discussed in this thread, > inconclusively: Yes, perhaps.

Re: Reducing logs produced by TAP tests running pg_regress on crash

2022-07-21 Thread Thomas Munro
On Fri, Jul 22, 2022 at 1:09 PM Michael Paquier wrote: > On Thu, Jun 23, 2022 at 02:30:13PM +0900, Michael Paquier wrote: > > One idea I got to limit the useless output generated is to check the > > status of the cluster after running the regression test suite as > > restart_on_crash is disabled b

Re: Reducing logs produced by TAP tests running pg_regress on crash

2022-07-21 Thread Michael Paquier
On Thu, Jun 23, 2022 at 02:30:13PM +0900, Michael Paquier wrote: > One idea I got to limit the useless output generated is to check the > status of the cluster after running the regression test suite as > restart_on_crash is disabled by default in Cluster.pm, and avoid any > follow-up logic in the

Reducing logs produced by TAP tests running pg_regress on crash

2022-06-22 Thread Michael Paquier
Hi all, (Thomas and Andres in CC.) Andres has complained a couple of days ago about the quantity of logs that can be fed into the TAP tests running pg_regress: https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhls...@alap3.anarazel.de This concerns the TAP tests of pg_upgrade, as wel