PG Bug reporting form <noreply@postgresql.org> writes:
> I found a discussion of the problem, but it seems that it was not solved.
> https://www.postgresql.org/message-id/flat/202411281216.sutbxtr6idnn%40alvherre.pgsql
That discussion began on 2024-11-28, and the fix was pushed a few days
later. It would require time travel for the fix to have been in 17.2
(released 2024-11-21). Should be in next week's 17.3, though.
regards, tom lane