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

Duplicate entries for stake pools for the same epoch sighted on sanchonet network #1901

Open
gregbgithub opened this issue Nov 15, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@gregbgithub
Copy link

OS
Your OS: Ubuntu

Versions
The db-sync version (eg cardano-db-sync --version): 13.6.0.0
PostgreSQL version: 16.4

Build/Install Method
The method you use to build or install cardano-db-sync: prebuilt binaries

Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): systemd

Additional context
Screenshot 2024-11-15 at 9 05 24 pm

Problem Report
After deploying db-sync version 13.6.0 on sanchonet after the network was re-spun and syncing from scratch (i.e. with --recreatedb), I noticed a week or so later while testing some koios queries that pool_stat table had duplicate records for each pool for the most recent epoch. This resulted in my koios query returning duplicate data because i was doing a join with pool_stat table to fetch some data for the pool information. I since manually deleted the higher-id value rows from pool_stat, and the issue didn't seem to repeat but I figured I might as well raise a github issue so the code / logic around inserts into that table could be double checked for possible gaps/edge case scenarios.

See attached screenshot of the dupe data for one of the pools from psql output. I'll keep an eye out for this repeating on any other db sync instances going forward.

@gregbgithub gregbgithub added the bug Something isn't working label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant