Opened 3 years ago

Closed 3 years ago

#32872 closed New feature (needsinfo)

Parallel Unit tests fail to clone DBs with TimescaleDB

Reported by: Kenneth Fortner Owned by: nobody
Component: Database layer (models, ORM) Version: 3.2
Severity: Normal Keywords: Timescale
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

If you use a TimescaleDB and run your unit tests in parallel Django will fail to clone the first test database to the additional databases.

Cloning test database for alias 'foo' ('foo_testDB')...Got an error creating the test database: source database "foo_testDB" is being accessed by other users
DETAIL: There is 1 other session using the database.

#### DB Section
DATABASES = {
        'default': {
            'ENGINE': 'django.db.backends.postgresql_psycopg2',
            'HOST': 'timescale',
            'USER': "user",
            'NAME': 'fooDB',
            'PASSWORD': "pwd",
            'PORT': '5432',
            'TEST': {
               'NAME': foo_testDB
            }
 }


#### Test call
python manage.py test --parallel 4

Change History (1)

comment:1 by Tim Graham, 3 years ago

Description: modified (diff)
Resolution: needsinfo
Status: newclosed

Django doesn't provide any support or testing for TimescaleDB, so it's not clear that Django is at fault. Feel free to reopen if you can at least provide some analysis of the situation. I imagine a custom database backend might be required which should be done as a third-party package rather than in Django itself.

Note: See TracTickets for help on using tickets.
Back to Top