Skip to content

Fix sequence migration for autoincrement tables in synapse_port_db #18677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2025

Conversation

mbakhoff
Copy link
Contributor

This PR fixes #18053 - the sliding sync tables will now migrate properly.

The synapse_port_db still fails in my case because there seem to be additional bug relating to stream_positions. There are a few open bugs when you search for IncorrectDatabaseSetup.

@mbakhoff mbakhoff requested a review from a team as a code owner July 12, 2025 10:11
Copy link
Contributor

@reivilibre reivilibre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, looks sensible!

Bit of a blunder on our part for using GENERATED ALWAYS I guess, though.

@reivilibre reivilibre merged commit a07e26a into element-hq:develop Jul 17, 2025
37 of 39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

portdb from SQLite to Postgres fails if Sliding Sync has been used: sliding_sync_connections.connection_key: cannot insert a non-DEFAULT value
2 participants