Zachareee
Hi, I’m working with a Postgres database which tends to take really long to retrieve data, it’s a simple :read action with a filter. There are no optimisations to the database that can be done on my side and so I’m looking to increase the timeout when querying the AshPostgres.Repo to avoid this error:
Postgrex.Protocol (#PID<0.359.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.739.0> timed out because it queued and checked out the connection for longer than 15000ms
I have tried setting timeout to :infinity in config/dev.exs as so:
config :hachiware, Hachiware.Reports.Repo,
hostname: "hachiware-db",
username: "postgres",
password: "postgres",
database: "postgres",
port: 5432,
show_sensitive_data_on_connection_error: true,
pool_size: 10,
timeout: :infinity
On the repo:
use AshPostgres.Repo, otp_app: :hachiware, timeout: :infinity
On the domain:
execution do
timeout :infinity
end
As well as on the Ash.read! action:
__MODULE__
|> Ash.read!(timeout: :infinity)
However it feels that nothing I’m doing works at all, any advice and help is appreciated!
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
- #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
- #hex
- #security
- #metaprogramming










Showing Posts 4 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Zachareee
Hi sflr, I realised I put the timeout on the wrong repo (yes I’m working on multiple repos), thank you for the help!
zachdaniel
Hmm…okay, maybe just faulty memory on my part. Seems strange that you’d be seeing this behavior
The default is 15000, and that’s the error you’re getting so it seems like it’s just somehow not being set? Setting timeout to infinity should AFAIK remove any kind of Postgrex timeout like that. Might be worth checking some base assumptions. Do you have multiple repos? Is this issue happening in production, implying a need to set this config in
prod.exs(orruntime.exs) as well? If nothing there helps, perhaps you could put together a reproduction and open an issue?Zachareee
Hey thanks for getting back, from this changelog it looks like
:pool_timeouthas been removed since v3.0.4, which is why I thought not to try it, seeing as AshPostgres.Repo is also an Ecto.Repo. Can I check if it is still a valid configuration?zachdaniel
Hmm…perhaps a different timeout option on the repo? IIRC there is something like
pool_timeout