Skip to content
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

synapse_port_db assumes events is append-only, but it is not #12007

Open
matrixbot opened this issue Dec 19, 2023 · 0 comments
Open

synapse_port_db assumes events is append-only, but it is not #12007

matrixbot opened this issue Dec 19, 2023 · 0 comments

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 19, 2023

This issue has been migrated from #12007.


synapse_port_db has a list of tables that it believes to be "append-only". That is to say, if the script is re-run on an updated copy of the input database, it will not clear these tables, but just add new rows that have arrived since last time.

Included in this list is events, which is generally read-only, but we do sometimes update existing rows - for example, when we convert an outlier to a non-outlier.

This means that any event that is de-outliered between runs of synapse_port_db may still be marked as an outlier in the target database, even though we have full state for it.

I'm not entirely sure if this has any measurable impact. It's possible that it simply means we will redundantly de-outlier it again.

@matrixbot matrixbot changed the title Dummy issue synapse_port_db assumes events is append-only, but it is not Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant