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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why did commit 6271fceb8 enable debug logging for all TAP tests?
Date: 2018-05-07 01:56:19
Message-ID: 20180507015619.GE27389@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2018-05-07 02:32:19 Having query cache in core
Previous Message Tom Lane 2018-05-07 01:49:46 Why did commit 6271fceb8 enable debug logging for all TAP tests?