Errors in logs when upgrading to 6.0.0: psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "pg_class_relname_nsp_index"

[sfirke]

Bug description

Upon upgrading to 6.0.0, I see a few instances of this at first startup:

superset_worker_beat  | 2026-01-06 04:10:45,663:ERROR:superset.app:Failed to create app
superset_worker_beat  | Traceback (most recent call last):
superset_worker_beat  |   File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context
superset_worker_beat  |     self.dialect.do_execute(
superset_worker_beat  |   File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
superset_worker_beat  |     cursor.execute(statement, parameters)
superset_worker_beat  | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "pg_class_relname_nsp_index"
superset_worker_beat  | DETAIL:  Key (relname, relnamespace)=(ab_group_id_seq, 2200) already exists.

Superset then seems to work normally, though I haven't tried out the group functionality so it's possible this indicates a problem there.

Doesn't seem to be causing me a problem but I wanted to open this issue in case others have this experience too. If it goes stale, we can convert to discussion.

Screenshots/recordings

No response

Superset version

6.0.0

Python version

I don't know

Node version

I don't know

Browser

Not applicable

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

This error happens when the upgrade process tries to create the ab_group_id_seq sequence, but it already exists in your database. This is managed by Flask-AppBuilder/SQLAlchemy, not by explicit Superset code or migrations. It's likely a side effect of how the migration or ORM tool interacts with your existing schema, not a bug in Superset itself. As long as Superset starts and works normally, this error is usually harmless and shouldn't affect group functionality, but it's a good idea to test creating and managing groups to be sure.

If you see any issues with groups or permissions, running superset db upgrade can help ensure all migrations are applied correctly and database objects are in sync. Manual sequence creation is discouraged—let the migration scripts handle it for you. Similar sequence-related issues have been resolved this way in the past (example). If everything works, you can safely ignore the error, but keep an eye out for any group-related problems after the upgrade.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}