Minimising contention on event_publish table and pessimistic lock exceptions

In our system we have a lot of small events flying (one of the reason the are small rather than batching is because indices cannot be created on large events - as you may remember modulith creates index on body of the event itself which causes issues on e.g. on postgress)

Event_Publication table is therefore very often updated which leads to pessimistic locks exceptions spamming output. Issues arise especially on completing a given event. I have questions here:

• what is most common way to deal with those problems?
• is it caused by longer than expected running transactions on our side?
• are these events that caused pessimistic lock issues on retried by modulith or spring framework?
• is there any way to supress output with all those warning if events are retried once locks free up?
• have you observed such behaviour in various systems you working on or others?
• anything else that maybe useful to help to deal with those contention issues, e.g. tips?

Start by examining contention around the Event_Publication table when events are completed, especially the pessimistic lock exceptions described in the issue. Investigate whether transaction duration, event retries, and warning output contribute to the behavior. Done would require a clear explanation of the cause and documented guidance for handling or suppressing expected lock retries.