fly_postgres_elixir
fly_postgres_elixir copied to clipboard
Library for working with local read-replica postgres databases and performing writes through RPC calls to other nodes in the primary Fly.io region.
Currently, it is recommended that you change your 'non-distributed' code: ```elixir def update(some, params) do Myapp.Repo.transaction(fn -> # ... complicated work involving DB manipulation here. end) end ``` into ```elixir...
Attempting to use the Fly repo from any region in which a replica is not yet running, seems to work perfectly fine... ... that is, until any mutating calls (`insert`,...
Hey Mark! Awesome repo! I'm working on adding this to a project and it all seems pretty straightforward except for [Oban](https://github.com/sorentwo/oban). ## The Problem For those who may not be...
I attempted to add [opentelemetry_ecto](https://github.com/open-telemetry/opentelemetry-erlang-contrib/tree/main/instrumentation/opentelemetry_ecto) to a project using `fly_postgres` and am getting no errors, but also no traces. When I am not using `fly_postgres`, I get the traces I...
Currently, there is an implied dependence on Fly.io databases because of how the DNS is modified so a "nearest" database can found. This helps when an instance is auto-deployed to...