Skip to content

Using alembic after upgrading to postgresql 16 results to error #1579

Discussion options

You must be logged in to vote

Alembic is working again by setting this environment variable in my .zshrc. I found this information after little googling and chatgpting

export DYLD_LIBRARY_PATH=/opt/homebrew/Cellar/postgresql@16/16.6/lib:$DYLD_LIBRARY_PATH

However, i still do not understand what is the root cause of this, i.e what causes alembic to look at this specific set of paths and why it misses the @16.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by Kotsakis
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external driver issues the issue involves a misbehavior on the part of the DBAPI itself, probably not SQLAlchemy or Alembic
2 participants