Hi! 30.04.2024 23:15, Justin Pryzby пишет:
Is this issue already fixed ? I wasn't able to reproduce it. Maybe it only happened with earlier patch versions applied ?
I think this was fixed in commit [1].[1] https://github.com/postgres/postgres/commit/fcf80c5d5f0f3787e70fca8fd029d2e08a923f91
-- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com
