On 2/20/26 12:57, Richard Guo wrote:
> ... and then pushed and back-patched to v16.
Thank you!
> Thank you, Sergey, for the report and the excellent self-contained
> repro query. This is a great catch. (I'm curious how you found this
> bug -- was it from a production query or a fuzzing tool?)
The bug was encountered by our customer upgrading to v17 and my
colleague passed this repro to me.
--
Sergey Shinderuk https://postgrespro.com/