#27751: Teardown of a PG test database fails if it is an autogenerated test_MYDB database -----------------------------------+------------------------------------ Reporter: Cynthia Kiser | Owner: nobody Type: Bug | Status: new Component: Testing framework | Version: 1.9 Severity: Normal | Resolution: Keywords: database, testing | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -----------------------------------+------------------------------------
Comment (by Cynthia Kiser): Replying to [comment:8 Ian Clark]: > This is happening because you are missing an entry in your pg_hba.conf file for your user to access the database 'postgres'. Ran into this problem myself today. I do not want my django user to write to the 'postgres' database. I consider the test framework trying to write to the postgres database a bug - one that was fixed in ticket #24791 - and then broken again in ticket #25329. -- Ticket URL: <https://code.djangoproject.com/ticket/27751#comment:9> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/061.16588bec36c6c2801cd38f0100b56e1c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.