When running the tests, I am obtaining "There is 1 other session using the database" with Postgresql
See original GitHub issueHello!
As the title says, almost everytime I run the tests I get
OperationalError: database "database_name" is being accessed by other users
DETAIL: There is 1 other session using the database
I was not getting it until I start using django-blog-zinnia in my project.
Searching through internet, I found https://code.djangoproject.com/ticket/22420#comment:8
according to that comment, that person was also using django-blog-zinnia. Is there a chance that this error is produced by blog-zinnia?
Thank you!
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
[Solved] PostgreSQL ERROR: There is 1 other session using ...
In PostgreSQL, if you have active connection to the database and if you try to DROP the database, you will get the following...
Read more >There is 1 other session using the database AWS RDS ...
When I try to remove the postgressql database using ansible module "postgresql_db" I am getting below error. FAILED!
Read more >PostgreSQL DROP Database DETAIL: There is 1 other ...
So the short answer is there is 1 active connection opened to target db, so it cannot delete the selected database until the...
Read more >List sessions / active connections in PostgreSQL database
You can see session list on our test server. sample results. Using pgAdmin. In the Browser pane, select our database (1) and then...
Read more >9.26. System Administration Functions - PostgreSQL
PostgreSQL allows database sessions to synchronize their snapshots. A snapshot determines which data is visible to the transaction that is using the snapshot....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This appears to be caused by directory pingers, which run on a secondary thread. I fixed this by disabling them in my
settings.py
:Hello,
in https://github.com/Fantomas42/django-blog-zinnia/commit/3c86754dbb65f99fbb88b60adf1e576467c0e3c1 the Thread functionality is totally disabled in the tests, the issue should not occurs anymore.
Regards