Thomas Munro <thomas.munro@gmail.com> writes:
> ... Admittedly that is nothing compared to the huge amount of extra log
> spam caused by regression.diffs filling up with these:
Yeah, that's really the main problem.
> I wonder if there would be a good way to filter those "never managed
> to connect" cases out... Exit code 2 (EXIT_BADCONN) is not the
> answer, because you get that also for servers that go away due to a
> crash where you do want to be able to see the diff, for information
> about where it crashed.
Maybe pg_regress could check that postmaster.pid is still there
before launching each new test script? (Obviously this all applies
only to "make check" not "make installcheck".)
regards, tom lane
