[BUG]:Migration 0005 fails to apply on Postgres DB #322

New issue

Closed

opened 2026-01-06 17:15:45 +00:00 by rsevs3 · 0 comments

rsevs3 commented

2026-01-06 17:15:45 +00:00

(Migrated from github.com)

The following error is generated when applying the migrations from 2026.1.5.1 to a postgres database. These migrations apply successfully on a mysql database.

Note the following comment from Claude:

PostgreSQL vs MySQL Constraint Behavior
PostgreSQL:

When you create a UNIQUE constraint, it automatically creates an index with the same name
The index and constraint share the same namespace
Once migration 0004 creates the constraint, the name unique_tagged_field_content_field is taken
When migration 0005 tries to create it again, PostgreSQL says "relation already exists" (in PostgreSQL, "relation" includes tables, indexes, and constraints)

MySQL:

Constraints and indexes have more separation
MySQL is more forgiving about recreating existing constraints
Django might handle duplicate constraint creation differently on MySQL

Why It Worked Locally
If you tested with MySQL or SQLite locally but production uses PostgreSQL, that explains it perfectly. The migrations run fine on MySQL but fail on PostgreSQL because of how PostgreSQL strictly enforces the uniqueness of relation names.

The stack trace:

  Applying tag_me.0004_fk_lookup_refactor...Added unique constraint 'unique_tagged_field_content_field'.
UserTag: No records needed FK population.
SystemTag: No records needed FK population.
Added index 'tag_me_user_tagged_user_idx'.
Added index 'tag_me_sys_tagged_field_idx'.
 OK
  Applying tag_me.0005_remove_taggedfieldmodel_unique_tagged_field_model_and_more...{"event": "uncaught_exception", "logger": "django", "level": "error", "exception_traceback": "Traceback (most recent call last):\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 103, in _execute\n    return self.cursor.execute(sql)\n           ~~~~~~~~~~~~~~~~~~~^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py\", line 117, in execute\n    raise ex.with_traceback(None)\npsycopg.errors.DuplicateTable: relation \"unique_tagged_field_content_field\" already exists\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n  File \"/home/django/./manage.py\", line 22, in <module>\n    main()\n    ~~~~^^\n  File \"/home/django/./manage.py\", line 18, in main\n    execute_from_command_line(sys.argv)\n    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py\", line 442, in execute_from_command_line\n    utility.execute()\n    ~~~~~~~~~~~~~~~^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py\", line 436, in execute\n    self.fetch_command(subcommand).run_from_argv(self.argv)\n    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 416, in run_from_argv\n    self.execute(*args, **cmd_options)\n    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 460, in execute\n    output = self.handle(*args, **options)\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 107, in wrapper\n    res = handle_func(*args, **kwargs)\n  File \"/venv_prod/lib/python3.13/site-packages/django/core/management/commands/migrate.py\", line 353, in handle\n    post_migrate_state = executor.migrate(\n        targets,\n    ...<3 lines>...\n        fake_initial=fake_initial,\n    )\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 135, in migrate\n    state = self._migrate_all_forwards(\n        state, plan, full_plan, fake=fake, fake_initial=fake_initial\n    )\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 167, in _migrate_all_forwards\n    state = self.apply_migration(\n        state, migration, fake=fake, fake_initial=fake_initial\n    )\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 255, in apply_migration\n    state = migration.apply(state, schema_editor)\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/migration.py\", line 132, in apply\n    operation.database_forwards(\n    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^\n        self.app_label, schema_editor, old_state, project_state\n        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n    )\n    ^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/operations/models.py\", line 1211, in database_forwards\n    schema_editor.add_constraint(model, self.constraint)\n    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py\", line 596, in add_constraint\n    self.execute(sql, params=None)\n    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/postgresql/schema.py\", line 45, in execute\n    return super().execute(sql, params)\n           ~~~~~~~~~~~~~~~^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py\", line 204, in execute\n    cursor.execute(sql, params)\n    ~~~~~~~~~~~~~~^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 79, in execute\n    return self._execute_with_wrappers(\n           ~~~~~~~~~~~~~~~~~~~~~~~~~~~^\n        sql, params, many=False, executor=self._execute\n        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n    )\n    ^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 92, in _execute_with_wrappers\n    return executor(sql, params, many, context)\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 100, in _execute\n    with self.db.wrap_database_errors:\n         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/utils.py\", line 91, in __exit__\n    raise dj_exc_value.with_traceback(traceback) from exc_value\n  File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 103, in _execute\n    return self.cursor.execute(sql)\n           ~~~~~~~~~~~~~~~~~~~^^^^^\n  File \"/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py\", line 117, in execute\n    raise ex.with_traceback(None)\ndjango.db.utils.ProgrammingError: relation \"unique_tagged_field_content_field\" already exists\n", "exception_type": "ProgrammingError", "exception_value": "relation \"unique_tagged_field_content_field\" already exists", "file": "/home/django/./manage.py", "function": "<module>", "line_number": 22, "timestamp": "2026-01-06 13:37:09"}
Traceback (most recent call last):
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
           ~~~~~~~~~~~~~~~~~~~^^^^^
  File "/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py", line 117, in execute
    raise ex.with_traceback(None)
psycopg.errors.DuplicateTable: relation "unique_tagged_field_content_field" already exists

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/django/./manage.py", line 22, in <module>
    main()
    ~~~~^^
  File "/home/django/./manage.py", line 18, in main
    execute_from_command_line(sys.argv)
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
    ~~~~~~~~~~~~~~~^^
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 416, in run_from_argv
    self.execute(*args, **cmd_options)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 107, in wrapper
    res = handle_func(*args, **kwargs)
  File "/venv_prod/lib/python3.13/site-packages/django/core/management/commands/migrate.py", line 353, in handle
    post_migrate_state = executor.migrate(
        targets,
    ...<3 lines>...
        fake_initial=fake_initial,
    )
  File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
        state, plan, full_plan, fake=fake, fake_initial=fake_initial
    )
  File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
        state, migration, fake=fake, fake_initial=fake_initial
    )
  File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 255, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/migration.py", line 132, in apply
    operation.database_forwards(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        self.app_label, schema_editor, old_state, project_state
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/operations/models.py", line 1211, in database_forwards
    schema_editor.add_constraint(model, self.constraint)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py", line 596, in add_constraint
    self.execute(sql, params=None)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/postgresql/schema.py", line 45, in execute
    return super().execute(sql, params)
           ~~~~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py", line 204, in execute
    cursor.execute(sql, params)
    ~~~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 79, in execute
    return self._execute_with_wrappers(
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        sql, params, many=False, executor=self._execute
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 100, in _execute
    with self.db.wrap_database_errors:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/venv_prod/lib/python3.13/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
           ~~~~~~~~~~~~~~~~~~~^^^^^
  File "/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py", line 117, in execute
    raise ex.with_traceback(None)
django.db.utils.ProgrammingError: relation "unique_tagged_field_content_field" already exists

The following error is generated when applying the migrations from 2026.1.5.1 to a postgres database. These migrations apply successfully on a mysql database. Note the following comment from Claude: ``` PostgreSQL vs MySQL Constraint Behavior PostgreSQL: When you create a UNIQUE constraint, it automatically creates an index with the same name The index and constraint share the same namespace Once migration 0004 creates the constraint, the name unique_tagged_field_content_field is taken When migration 0005 tries to create it again, PostgreSQL says "relation already exists" (in PostgreSQL, "relation" includes tables, indexes, and constraints) MySQL: Constraints and indexes have more separation MySQL is more forgiving about recreating existing constraints Django might handle duplicate constraint creation differently on MySQL Why It Worked Locally If you tested with MySQL or SQLite locally but production uses PostgreSQL, that explains it perfectly. The migrations run fine on MySQL but fail on PostgreSQL because of how PostgreSQL strictly enforces the uniqueness of relation names. ``` The stack trace: ``` Applying tag_me.0004_fk_lookup_refactor...Added unique constraint 'unique_tagged_field_content_field'. UserTag: No records needed FK population. SystemTag: No records needed FK population. Added index 'tag_me_user_tagged_user_idx'. Added index 'tag_me_sys_tagged_field_idx'. OK Applying tag_me.0005_remove_taggedfieldmodel_unique_tagged_field_model_and_more...{"event": "uncaught_exception", "logger": "django", "level": "error", "exception_traceback": "Traceback (most recent call last):\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 103, in _execute\n return self.cursor.execute(sql)\n ~~~~~~~~~~~~~~~~~~~^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py\", line 117, in execute\n raise ex.with_traceback(None)\npsycopg.errors.DuplicateTable: relation \"unique_tagged_field_content_field\" already exists\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n File \"/home/django/./manage.py\", line 22, in <module>\n main()\n ~~~~^^\n File \"/home/django/./manage.py\", line 18, in main\n execute_from_command_line(sys.argv)\n ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py\", line 442, in execute_from_command_line\n utility.execute()\n ~~~~~~~~~~~~~~~^^\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py\", line 436, in execute\n self.fetch_command(subcommand).run_from_argv(self.argv)\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 416, in run_from_argv\n self.execute(*args, **cmd_options)\n ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 460, in execute\n output = self.handle(*args, **options)\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/base.py\", line 107, in wrapper\n res = handle_func(*args, **kwargs)\n File \"/venv_prod/lib/python3.13/site-packages/django/core/management/commands/migrate.py\", line 353, in handle\n post_migrate_state = executor.migrate(\n targets,\n ...<3 lines>...\n fake_initial=fake_initial,\n )\n File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 135, in migrate\n state = self._migrate_all_forwards(\n state, plan, full_plan, fake=fake, fake_initial=fake_initial\n )\n File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 167, in _migrate_all_forwards\n state = self.apply_migration(\n state, migration, fake=fake, fake_initial=fake_initial\n )\n File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py\", line 255, in apply_migration\n state = migration.apply(state, schema_editor)\n File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/migration.py\", line 132, in apply\n operation.database_forwards(\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~^\n self.app_label, schema_editor, old_state, project_state\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n )\n ^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/migrations/operations/models.py\", line 1211, in database_forwards\n schema_editor.add_constraint(model, self.constraint)\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py\", line 596, in add_constraint\n self.execute(sql, params=None)\n ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/postgresql/schema.py\", line 45, in execute\n return super().execute(sql, params)\n ~~~~~~~~~~~~~~~^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py\", line 204, in execute\n cursor.execute(sql, params)\n ~~~~~~~~~~~~~~^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 79, in execute\n return self._execute_with_wrappers(\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~^\n sql, params, many=False, executor=self._execute\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n )\n ^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 92, in _execute_with_wrappers\n return executor(sql, params, many, context)\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 100, in _execute\n with self.db.wrap_database_errors:\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/django/db/utils.py\", line 91, in __exit__\n raise dj_exc_value.with_traceback(traceback) from exc_value\n File \"/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py\", line 103, in _execute\n return self.cursor.execute(sql)\n ~~~~~~~~~~~~~~~~~~~^^^^^\n File \"/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py\", line 117, in execute\n raise ex.with_traceback(None)\ndjango.db.utils.ProgrammingError: relation \"unique_tagged_field_content_field\" already exists\n", "exception_type": "ProgrammingError", "exception_value": "relation \"unique_tagged_field_content_field\" already exists", "file": "/home/django/./manage.py", "function": "<module>", "line_number": 22, "timestamp": "2026-01-06 13:37:09"} Traceback (most recent call last): File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 103, in _execute return self.cursor.execute(sql) ~~~~~~~~~~~~~~~~~~~^^^^^ File "/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py", line 117, in execute raise ex.with_traceback(None) psycopg.errors.DuplicateTable: relation "unique_tagged_field_content_field" already exists The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/django/./manage.py", line 22, in <module> main() ~~~~^^ File "/home/django/./manage.py", line 18, in main execute_from_command_line(sys.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() ~~~~~~~~~~~~~~~^^ File "/venv_prod/lib/python3.13/site-packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 416, in run_from_argv self.execute(*args, **cmd_options) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 460, in execute output = self.handle(*args, **options) File "/venv_prod/lib/python3.13/site-packages/django/core/management/base.py", line 107, in wrapper res = handle_func(*args, **kwargs) File "/venv_prod/lib/python3.13/site-packages/django/core/management/commands/migrate.py", line 353, in handle post_migrate_state = executor.migrate( targets, ...<3 lines>... fake_initial=fake_initial, ) File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( state, plan, full_plan, fake=fake, fake_initial=fake_initial ) File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( state, migration, fake=fake, fake_initial=fake_initial ) File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/executor.py", line 255, in apply_migration state = migration.apply(state, schema_editor) File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/migration.py", line 132, in apply operation.database_forwards( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ self.app_label, schema_editor, old_state, project_state ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/venv_prod/lib/python3.13/site-packages/django/db/migrations/operations/models.py", line 1211, in database_forwards schema_editor.add_constraint(model, self.constraint) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py", line 596, in add_constraint self.execute(sql, params=None) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/db/backends/postgresql/schema.py", line 45, in execute return super().execute(sql, params) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/db/backends/base/schema.py", line 204, in execute cursor.execute(sql, params) ~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 79, in execute return self._execute_with_wrappers( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ sql, params, many=False, executor=self._execute ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers return executor(sql, params, many, context) File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 100, in _execute with self.db.wrap_database_errors: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/venv_prod/lib/python3.13/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/venv_prod/lib/python3.13/site-packages/django/db/backends/utils.py", line 103, in _execute return self.cursor.execute(sql) ~~~~~~~~~~~~~~~~~~~^^^^^ File "/venv_prod/lib/python3.13/site-packages/psycopg/cursor.py", line 117, in execute raise ex.with_traceback(None) django.db.utils.ProgrammingError: relation "unique_tagged_field_content_field" already exists ```