ryanditjia
Hello everyone, when I run my unit test, I sometimes (not all the time) run into this error:
(Postgrex.Error) ERROR 40P01 (deadlock_detected) deadlock detected
hint: See server log for query details. Process 11437 waits for ShareLock on transaction 56033; blocked by process 11436. Process 11436 waits for ShareLock on transaction 56040; blocked by process 11437.
The test attempts to insert 3 records:
work_orders =
for _ <- 1..3 do
{:ok, work_order} = Documents.create_work_order(attrs)
work_order
end
expected_counters = [1, 2, 3]
assert expected_counters == work_orders |> Enum.map(& &1.counter)
create_work_order is an Ecto.Multi that:
- Inserts counter to
countersDB (business requirement dictates that counter restarts from 1 every year) - Grabs the returned counter to insert together to
work_ordersDB - Repo.transaction()
Is the above loop a bad way to test? Or is my transaction function incorrect even though it works (pasted below)?
def create_work_order(attrs \\ %{}) do
counter_changeset = Counter.changeset(%Counter{}, attrs)
work_order_changeset = WorkOrder.creation_changeset(%WorkOrder{}, attrs)
Multi.new()
# Get the next counter of the year
# If year doesn’t yet exist, create one and set counter to 1 (database default)
|> Multi.insert(:next_counter, counter_changeset,
# If year exists, increment the counter by 1
conflict_target: :year,
on_conflict: [inc: [counter: 1]]
)
# Insert work order, with counter added to the changeset
|> Multi.insert(
:work_order,
fn %{next_counter: %{counter: counter}} ->
work_order_changeset
|> Ecto.Changeset.put_change(:counter, counter)
end
)
|> Repo.transaction()
|> case do
{:ok, %{work_order: work_order}} ->
{:ok, work_order}
{:error, :next_counter, _changeset, _changes} ->
# Return work_order_changeset for more thorough field checks
{:error, %{work_order_changeset | action: :insert}}
{:error, :work_order, changeset, _changes} ->
{:error, changeset}
end
end
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Hello
I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley:
Mutonex gamedesign was finish...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #hex










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
Have you configured the Ecto Sandbox?
It will isolate each test in a transaction and rollback the transaction so each test has a consistent view of the data. It will also make it much less likely you will encounter deadlocks.
ryanditjia
Thanks kip. Yes, I believe this is Phoenix’s default, but I rechecked just in case. I also run into a unique index constraint error with another test but that’s rarer, I’d say 5% of the time, while deadlock is 10%.
Not a dealbreaker by any stretch of the imagination, and if it gets too annoying I can simply set async to false.
If you think there could be something wrong or missing with the way my Ecto.Multi is set up, please let me know, I’m new to Elixir and Phoenix and am keen to dive deeper.
Thanks again