ProgrammingError: column "deleted" of relation "contentcuration_user" already exists

[sentry-io]

Something isn't right with this migration. Perhaps the initial job timed out-- something that can happen when a Django migration adds a not-null column that requires setting defaults on the entire table.

Sentry Issue: STUDIO-FWZ

DuplicateColumn: column "deleted" of relation "contentcuration_user" already exists

  File "django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "django_prometheus/db/common.py", line 71, in execute
    return super().execute(*args, **kwargs)

ProgrammingError: column "deleted" of relation "contentcuration_user" already exists

(15 additional frame(s) were not displayed)
...
  File "django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "django_prometheus/db/common.py", line 71, in execute
    return super().execute(*args, **kwargs)

[bjester]

Unfortunately the original migration job logs are no longer available, but it did finish in a reasonable time

[bjester]

We need to determine if this is still an issue

[vkWeb]

@bjester how can we determine that sir? I think this relates to #3726?

[vkWeb]

I discussed this issue with @bjester sir, we aren't seeing this error any more, if we see it in future, we'll file another issue, closing for now.