Re: Is this a bug in pg_current_logfile() on Windows? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Is this a bug in pg_current_logfile() on Windows?
Date
Msg-id 1870287.1594323370@sss.pgh.pa.us
Whole thread Raw
In response to Re: Is this a bug in pg_current_logfile() on Windows?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is this a bug in pg_current_logfile() on Windows?  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
I wrote:
> Cool, I'll go try changing all those conditions to use the msys test.

OK, that worked: all four relevant buildfarm members are now showing
the expected test failure.  So I'll go fix the original bug.

Should we consider back-patching the CRLF filtering changes, ie
91bdf499b + ffb4cee43?  It's not really necessary perhaps, but
I dislike situations where the "same" test on different branches is
testing different things.  Seems like a recipe for future surprises.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Grigory Smolkin
Date:
Subject: Re: Postgres is not able to handle more than 4k tables!?
Next
From: Andrew Dunstan
Date:
Subject: Re: Is this a bug in pg_current_logfile() on Windows?