I use a standalone connection pooling for Postgresql in some cases. It is
faster and more efficient than
doing full connects to Postgresql directly in each request.
https://www.pgbouncer.org/
Arndt.
Am Di., 21. Nov. 2023 um 16:14 Uhr schrieb Eldav :
> Thank you Jonathan,
>
> after asking my
This should not happen. Do you know which cookiecutter you used, and when?
This should not happen in the most recent cookiecutter.
As far as I remember, I used the official cookiecutter, but that was a few
years ago (around the time when Pyramid 2.0 was released, and I felt the
need to
Thank you Jonathan,
after asking my question, I did more googling and found this :
https://docs.sqlalchemy.org/en/20/core/pooling.html#pooling-multiprocessing
It does mention Engine.dispose :) I tried their solution #4, which seemed
to be the one which fit best in my code. But somehow I feel
> Namely, if you deploy with Gunicorn a Pyramid + PostgreSQL app based on
the standard cookiecutter, you will run into problems, because the
connection to the DB can't be shared between the processes, so each process
needs to have its own connection to the DB.
I forgot to mention...
This
