Re: Why did commit 6271fceb8 enable debug logging for all TAP tests?

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers@lists.postgresql.org

Date: 2018-05-07T01:56:19Z

Lists: pgsql-hackers

On Sun, May 06, 2018 at 09:49:46PM -0400, Tom Lane wrote:
> Now, that was neither mentioned in the commit message nor justified
> by any added test cases or scaffolding, so I'm assuming it was simply a
> mistake and should be reverted.  Please confirm.

That was around to check that the debug messages generated when parsing
the backup_label file are correctly happening when running recovery
tests and made the patch validation handy.  Let's remove it.
--
Michael

Commits

Improve inefficient regexes in vacuumdb TAP test.
- da0b4c8a8add 10.5 landed
- c63913ca7d1d 11.0 landed
- 42e5a1b563da 9.5.14 landed
- 3d48654017aa 9.4.19 landed
- 36784e9147fa 9.6.10 landed
Undo extra chattiness of postmaster logs in TAP tests.
- 17551f1a21fa 11.0 landed
Add TIMELINE to backup_label file
- 6271fceb8a4f 11.0 cited