Hello Alexander, 05.02.2024 02:51, Alexander Korotkov wrote:
Usage of heap_inplace_update() seems appropriate for me here. It avoids trouble with both TOAST and row-level locks. Alexander, could you please recheck this fixes the problem.
I've re-tested the last problematic scenario and can confirm that the fix works for it (though it still doesn't prevent the autovacuum issue (with 4b885d01 reverted)), but using heap_inplace_update() was considered risky in a recent discussion: https://www.postgresql.org/message-id/1596629.1698435146%40sss.pgh.pa.us So maybe it's worth to postpone such a fix till that discussion is finished or to look for another approach... Best regards, Alexander
