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.

Sign up for GitHub

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

Jump to bottom

Apparent bug resulting in multiple most_recent = true rows #463

Open
Tabby opened this issue May 11, 2022 · 1 comment
Open

Apparent bug resulting in multiple most_recent = true rows #463

Tabby opened this issue May 11, 2022 · 1 comment

Comments

@Tabby
Copy link
Contributor

Tabby commented May 11, 2022

Seems like it's occasionally possible for concurrent updates to leave a transitions table in a state where two identical transitions are added (differing only in modification time) but with different primary keys and with the most_recent column set to true for both.

Not really sure how this is possible :S

Slack thread where the issue has been seen a couple of times: https://gocardless.slack.com/archives/C02AU55J6R4/p1652169426426829?thread_ts=1650356440.633239&cid=C02AU55J6R4

Slack thread asking about this issue and potential causes/solutions before reporting this issue: https://gocardless.slack.com/archives/C031GKFNK6J/p1652280367772639
@dmitry
Copy link
Contributor

dmitry commented Sep 2, 2023

Do you have unique index key for the most_recent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dmitry @Tabby