Postgres Pro
Downloads
Home   >   mailing lists

Re: Why did commit 6271fceb8 enable debug logging for all TAP tests? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Why did commit 6271fceb8 enable debug logging for all TAP tests?
Date
Msg-id 20180507015619.GE27389@paquier.xyz
Whole thread Raw
In response to Why did commit 6271fceb8 enable debug logging for all TAP tests?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why did commit 6271fceb8 enable debug logging for all TAP tests?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Why did commit 6271fceb8 enable debug logging for all TAP tests?
Next
From: Tatsuo Ishii
Date:
Subject: Having query cache in core