Changes don't get committed to database when using pool.

[pooryorrick]

I can see that there is a closed issue with similar problem, but no resolution was found. So I will dare to open a new one.

I'm running Django 3.1.5 app and postgres db on Azure, and experiencing 1,5-2 second latency on all views that require database connection. This particular package was suggested by Microsoft support, and it does indeed reduce response time down to 150-200 ms, which is great. There is no problem with retrieving data from the db, however saving data is very inconsistent across the app, but still looks consistent for a given view, meaning that some views consistently succeed with saving data, while other views consistently fail...

I have tried to add AUTOCOMIT=True to settings config, but it didn't help

Any suggestions on how to fix the problem , or where to start looking?

[pooryorrick]

@altairbow any ideas or suggestions?