princemaple
Ok this is… more than weird
It’s also consistent during insert_all with conflicts. I’m trying to back fill some missing data from backup, but can’t because the db thinks they are already there…
I can’t have 20+ uuids with conflicts, right? That’d be too luck. I checked they are totally different from what’s coming back from the db. Repo.all(from x in X, where: x.id in ^my_ids) I get these 20+ results with totally different ids, but consistent!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 23 to 14- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
princemaple
Cough me too in production cough
FlyingNoodle
We found out in production
garrison
Incidentally postgres 18 is the release that finally enables checksums by default, though from what I can tell not when migrating an existing DB.
garrison
Wow, I had heard Matrix ran into corrupted indexes recently but their DB is pretty big. Didn’t think it was this common! If that’s what it was you’re lucky you caught it while testing. Could have been a very scary bug.
princemaple
Thanks! I think these are the answers (vacuum / rebuild indices). I worked around by setting new IDs (because the things had this problem were not referenced elsewhere as fk, so it’s safe to do so) and I’m not sure if I will be able to confirm it’s the proper fix.
I indeed upgraded the db recently.
sevenseacat
Actually yeah I’ve seen weird behaviour like this with a corrupted index after an upgrade. Rebuilding indexes fixed it for me.
wanton7
What’s the type of the id database column?
jswanner
@princemaple any luck figuring this one out?
FlyingNoodle
I have had some funky behaviour like this after a pg upgrade. I fixed it by running a vacuum.
Asd
Can you please show the schema definition for the module you’re querying? It might be that it uses some special encoding of the IDs or it might use some other field as the primary key