On Mon, Nov 09, 2026 at 11:26:50AM +0300, Aleksander Alekseev wrote:> A customer reported offlist that the issue is reproducible in practice> on PostgreSQL 18. I suggest backpatching this.
I would not mind. Any concerns from others?--Michael