This is an issue with postgres 10 where they changed version naming scheme. It’s fixed in the latest postgrex release. Running mix deps.update postgrex
should solve the issue.
5 Likes
This is an issue with postgres 10 where they changed version naming scheme. It’s fixed in the latest postgrex release. Running mix deps.update postgrex
should solve the issue.