[BUG] Containers make DB queries that trigger communication errors

[Encephala]

Tag/version of Container Images
Choose from: 0.4.*

When having the mailman containers running (using just the mailman-core and mailman-web containers from the docker-compose- postorius.yml), our database keeps outputting the following errors:

2024-03-10 15:59:04 334 [Warning] Aborted connection 334 to db: 'mailman' user: 'mailman' host: '...' (Got an error reading communication packets)

Our database is the official mariadb image, tag 11.2.3-jammy.

This does not seem to be the direct cause of any issues in mailman, but it doesn't seem right either.
I ran into this SO post: https://dba.stackexchange.com/questions/19135/mysql-error-reading-communication-packets,
but the proposed solution of setting max_allowed_packet to a large value does not get rid of this problem.

[barats]

Same problem here.

I even tried to use PostgreSQL instead of MySQL, failed as well due to the same problem, Database Connection.

Is there any upgrade for this?

[barats]

Same problem here.

I even tried to use PostgreSQL instead of MySQL, failed as well due to the same problem, Database Connection.

Is there any upgrade for this?

I could provide more details, if it's needed.