3 ms·
It's not PostgreSQL's fault that Django closes the connection after each request explicitly (see close_connection() for what was done before 1.6): [1] https://
by stefantalpalaru 14y ago
It's not PostgreSQL's fault that Django closes the connection after each request explicitly (see close_connection() for what was done before 1.6):
[1] https://github.com/django/django/blob/master/django/db/__init__.py https://github.com/django/django/blob/master/django/db/__ini...
- raverbashing 14y agoI understand that, and I'm not saying that there aren't several issues in Django (but some are getting better) What I'm saying is that with PgBouncer you have Django <> PgBouncer <> Postgresql, right? So what PgBouncer is doing (dealing with several open/close connections) maybe could be done better inside PostgreSQL