Re: Remove specific _\n code in TAP for Windows - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Remove specific _\n code in TAP for Windows
Date
Msg-id aP__5-hsUWksPjUP@paquier.xyz
Whole thread Raw
In response to Re: Remove specific _\n code in TAP for Windows  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Remove specific _\n code in TAP for Windows
List pgsql-hackers
On Mon, Oct 27, 2025 at 08:33:57AM -0700, Jacob Champion wrote:
> Ah, sorry, I put part of my first attempt at it over in [1]. But I
> realize that's not very visible, nor does it address
> 003_ldap_connection_param_lookup.

Ahh, so you did post something.  I have missed that


> I'm carrying a local diff that switches 003_ldap_ over to qq{} style.
> Attached in case you like it, but your patch LGTM too.

Your suggestions for the LDAP test are cleaner than what I came up
with, so reused these.

>> That would be up to the buildfarm to act as final judge, but any
>> objections in attempting to get rid of these like in the attached?
>> I would try first HEAD to be sure, then follow with an optional
>> backpatch.
>
> Sounds like a plan.

Time for a verdict, so applied on HEAD now.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: another autovacuum scheduling thread
Next
From: Michael Paquier
Date:
Subject: Re: [BUG] temporary file usage report with extended protocol and unnamed portals