Hi Michael,

> This problem is unlikely going to show up in practice, so no backpatch.

A customer reported offlist that the issue is reproducible in practice
on PostgreSQL 18. I suggest backpatching this.

--
Best regards,
Aleksander Alekseev


Reply via email to