On 2025-04-07 Mo 11:05 AM, Andrew Dunstan wrote:
>
> On 2025-04-07 Mo 12:58 AM, Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> On 2025-04-01 Tu 11:15 AM, Andrew Dunstan wrote:
>>>> On 2025-04-01 Tu 8:47 AM, vignesh C wrote:
>>>>> There is an existing CF entry for this at [1]. If no one picks this
>>>>> till the end of this CF, we can move it to next CF.
>>>>> [1] - https://commitfest.postgresql.org/patch/5610/
>>>> Somehow I missed that. OK, looks good, will commit shortly.
>>> Done
>> fairywren has been failing rather horribly since this went in [1].
>> It's not certain of course that this commit broke it and not one
>> of the other ones that first appeared in that build -- but none
>> of the other ones look plausibly related.
>>
>> regards, tom lane
>>
>> [1]
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-04-02%2007%3A06%3A04
>
>
>
> Yes, that was indeed the problem. I have reverted the patch.
>
>
>
Lars,
I have marked the CF entry as Returned with Feedback - you can submit
again, but will need to show that this does not cause breakage on x86_64
using any msys2 toolchain.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
