Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench
Date
Msg-id 8617bf50-0a00-afdc-0bc8-41ffc7f70f39@dunslane.net
Whole thread Raw
In response to Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench  (Michael Paquier <michael@paquier.xyz>)
List pgsql-committers
On 6/24/21 11:08 PM, Michael Paquier wrote:
> On Thu, Jun 24, 2021 at 10:26:18PM -0400, Andrew Dunstan wrote:
>> Since the file isn't read in using slurp_file, that $ won't match
>> because the lines will end \r\n instead of \n.
> I did not remember this one with Msys, thanks.  I am not sure that
> there is any need for an eval block here actually once you remove
> open()?  What do you think about something like the attached?


+        # On Msys, filter out any CRLF.
+        $contents_raw =~ s/\r\n/\n/g if $Config{osname} eq 'msys';

This is completely redundant. The whole point is that slurp_file does
exactly this for you.


+        my @contents = split("\n", $contents_raw);

Probably more idiomatic to write split(/\n/,$contents_raw), or
split(/^/, $contents_raw) if you want to keep the line feeds.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Put option listing back into alphabetical order
Next
From: Michael Paquier
Date:
Subject: pgsql: Cleanup some code related to pgbench log checks in TAP tests