-
Notifications
You must be signed in to change notification settings - Fork 102
Preventing duplication of game rating logs #1294
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
Open
BElluu
wants to merge
2
commits into
beyond-all-reason:main
Choose a base branch
from
BElluu:issue-433-20260616
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+26
−1
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22 changes: 22 additions & 0 deletions
22
priv/repo/migrations/20260616101633_unique_index_rating_logs.exs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| defmodule Teiserver.Repo.Migrations.UniqueIndexRatingLogs do | ||
| use Ecto.Migration | ||
|
|
||
| def up do | ||
| # Remove duplicate entries keeping the earliest | ||
| # (lowest id) per (match_id, user_id, rating_type_id) | ||
| execute(""" | ||
| DELETE FROM teiserver_game_rating_logs | ||
| WHERE id NOT IN ( | ||
| SELECT DISTINCT ON (match_id, user_id, rating_type_id) id | ||
| FROM teiserver_game_rating_logs | ||
| ORDER BY match_id, user_id, rating_type_id, id ASC | ||
| ) | ||
| """) | ||
|
|
||
| create unique_index(:teiserver_game_rating_logs, [:match_id, :user_id, :rating_type_id]) | ||
| end | ||
|
|
||
| def down do | ||
| drop unique_index(:teiserver_game_rating_logs, [:match_id, :user_id, :rating_type_id]) | ||
| end | ||
| end | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the SQL for this? I'm pretty sure this is going to acquire an exclusive lock on the entire table for the duration of the operation. This table has 13M rows at time of writing.
How long would the index creation take? If it's more than a couple of seconds, we need to change it and make it non blocking.
with postgres, you can create an index concurrently, and then create a unique constraint using the existing index.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creating index for that many rows, can take some minutes.
So maybe we should firstly manualy delete duplicates
and then create index concurently out of transaction without lock
What do you think ?