Hello there,

I just read this similar post which is nicely explained and I'd like to put out the related issue below

I just mounted a cluster of 4 odoo instances sharing the same database and they seem to be working just fine. These are all odoo 16.0 20240216 build. 1 Postgres db accessed by the 4 dockered odoo instances. There's also an nginx server taking care of routing.

Each instance has 2 workers 2 max cron threads and the relevant settings for memory and time limits.

All nifty and nice but for one small detail (I hope it's small):

I keep getting this pesky thing on all of my logs every minute:

39 INFO ? odoo.sql_db: ConnectionPool(used=1/count=1/max=64): Closed 3 connections to 'user=odoo password=xxx dbname=odoo1 host=postgres port=5432 application_name=odoo-39 sslmode=prefer'

39 INFO ? odoo.sql_db: ConnectionPool(used=1/count=1/max=64): Closed 1 connections to 'user=odoo password=xxx dbname=odoo2 host=postgres port=5432 application_name=odoo-39 sslmode=prefer'

39 INFO ? odoo.sql_db: ConnectionPool(used=1/count=1/max=64): Closed 1 connections to 'user=odoo password=xxx dbname=odoo3 host=postgres port=5432 application_name=odoo-39 sslmode=prefer'

39 INFO ? odoo.sql_db: ConnectionPool(used=1/count=1/max=64): Closed 1 connections to 'user=odoo password=xxx dbname=odoo3 host=postgres port=5432 application_name=odoo-39 sslmode=prefer'

sometimes the application_name is 38 (I think these are related to the cron workers) because when I start the server up I get this:
33 INFO ? odoo.service.server: Worker WorkerHTTP (33) alive

34 INFO ? odoo.service.server: Worker WorkerHTTP (34) alive

38 INFO ? odoo.service.server: Worker WorkerCron (38) alive

39 INFO ? odoo.service.server: Worker WorkerCron (39) alive

is this a problem? Leave it as it is?  and if yes how to make the logs not show this?

Thanks for any help.