DidactMacros
This command seems to always fail
MIX_ENV=prod mix ecto.reset
The database for ContExp.Repo couldn't be dropped: ERROR 55006 (object_in_use) cannot drop the currently open database
I just tried this in the dev environment and it worked, I restarted the shell, and have no web pages running.
Is the production env itself keeping the db open in a way that prohibits dropping it?
It seems we are not supposed to drop dbs in prod, perhaps db configs are discarded between different product versions?
Would appreciate some light on this. I’ll also be reviewing the docs for clues.
EDIT: MIX_ENV=prod mix ecto.drop --force-drop also yields the same connection error (despite being used for the sake of ignoring connections).
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #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
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
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 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
This is a postgres question not an ecto one. That error is postgres telling you that you cannot drop a db while other concurrent connections to the database exist. Stop those other connections and the drop should start working.
Though I’d argue that these kind of operations should generally not be done through mix commands in a production environment. Imo it’s better to use a limited user account with the application, preventing it doing any harmful operations on accident. One off tasks like deletion of a db then happen on the side using some admin credentials independently from the application.
DidactMacros
I don’t know if this is the right way to do it but
MIX_EVN=prod mix ecto.rollback --all
…is a quite sufficient compromise for me (perhaps not even a compromise at all)