On Thu, May 14, 2026 at 9:58 AM Michael Paquier <[email protected]> wrote: > On Thu, May 14, 2026 at 09:12:58AM +0300, Alexander Korotkov wrote: > > On Fri, May 8, 2026 at 9:19 AM Michael Paquier <[email protected]> wrote: > >> If you wish me to look at this patch set in details, I may be able to > >> do so around the beginning of next week. I'm not sure that there is a > >> strong urgency in tackling this issue for this minor release, this > >> could wait a bit more.. > > > > Any news from your side? > > (Forgot -hackers and other folks in CC, sorry about that.) > > Unfortunately I have not been able to get back to it this week, and > next week is moot. Perhaps it is better to not wait for me here, so > feel free to go ahead as you feel.
Thank you for noticing. I've pushed this today. I have to slightly revise the tests to run on 18 and 17 (different log messages, and default value of log_lock_waits). ------ Regards, Alexander Korotkov Supabase
