@CastLouis: Did you checked this article? It’s guide for probably what you want.

i check my configurations and looks like in the example, the problem is that when i run the process it took more time than 15ms, and i modify the conection timeout in test.exs and in all the files and it doesn’t work.

@CastLouis: It looks like another problem with (default?) configuration - ping @josevalim and @fishcakez.

To be sure, please update your dependencies (especially Ecto and Postgrex).

Please also give us some info:

1. Your OS and source of Erlang and Elixir you use like: Distro Name - Version - default/name of repo
2. Erlang and Elixir versions
3. Your dependencies version (again especially Ecto and Postgrex)
4. Your database version
5. If possible please share a minimal example to reproduce your problem with timeout

Thanks @Eiji.

Keep in mind that the ownership timeout is controlled by the :ownership_timeout configuration. I think we improve the error message for it in more recent versions as well.

Good morning
i was loading a .csv file with a lot of registry, it took a lot of time to complete, while it loading the

code of loading the file
defp parse_line_to_string(line) do
<<code::binary-size(2), _::binary-size(1), rest::binary>> = line
{code, rest}
end

the code to insert into the database:

defp parse_line_to_string(line) do
<<code::binary-size(2), _::binary-size(1), rest::binary>> = line
{code, rest}
end

#the configuration from ecto:
config :na_db,
ecto_repos: [NA.DB.Repo]

config :na_db, NA.DB.Repo,
adapter: Ecto.Adapters.Postgres,
database: “nadb”,
username: “dadmin”,
password: “d@dm!n”,
hostname: “127.0.0.1”,
pool: Ecto.Adapters.SQL.Sandbox,
port: “5432”,
timeout: 450000

i was changing and use :ownership_timeout and set more time and it doesn’t work.

I tried to simulate similar work (collecting data for more than 15s) and I got same error, however Supervisor for MyApp.Repo saves tests from not passing and I checked also database and all works! Elixir is just awesome!

@josevalim: Thanks! I added it to configuration and it still works same, but without errors like in this topic. I agree that we need a better error message, because I also through about other timeout configuration variables.
I have a question that is related to this topic. Is it safe to set much more bigger timeouts in configuration than default one or we need to accept some consequences? Imagine new blog will probably be rarely visited and that surprise of Elixir admin that it have a error every 15s

@CastLouis: Make sure that you are changing it in right configuration file and be sure to follow all steps in tutorial I previously linked. As I already wrote I got same error in example application and solved it using both tutorial and José tip.

i was modifing the postgrex.ex, the property @timeout with more time, but the problem still,

@CastLouis: What you mean by postgrex.ex? You need to change configuration *.exs file in /config directory. Depends on environment that you are working on you should apply configuration change in appropriate configuration file like: test.exs.
Example config/test.exs file:

use Mix.Config

config :my_app, MyApp.Repo,
  adapter: Ecto.Adapters.Postgres,
  database: "my_app_test",
  hostname: "localhost",
  ownership_timeout: 60_000, # <- add this line
  password: "postgres",
  pool: Ecto.Adapters.SQL.Sandbox,
  username: "postgres"

i was modify postgrex @timeout property for chech, i was modifing the test.exs with ownership_timeout, pool_timeout and timeout too, but the problem persist and i dont know how can i find more information about it, i think the reset the machine if ecto see the changes let me.

@CastLouis: You missed something. Checked again Ecto tutorial step by step and be sure to add :ownership_timeout to test.exs. If you can publish your code or invite me to repository then I can fix it for you - I will create a PR. I have accounts on Github, BitBucket and GitLab