-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres 17 support #797
Comments
Oh hey, I didn't know there was an issue for this. This is underway (by me) and expected soon. I'll update this with progress. |
@jasonmp85 Sounds good. Someone had asked for my extension (pg_smtp_client) to support pg17, which I did, but then during testing I realized trunk doesn't work with pg17 yet so I created this issue. I figured maybe someone was working on it, but didn't know for sure. |
We have a similar error with pgvector: Failed to fetch Trunk archive from v1 API: Failed to find an archive for pgvector vlatest built for PostgreSQL 17 |
@academiaresf It looks like pgvector was recently updated for Postgres 17, so it should work now. @jasonmp85 I saw that trunk works with 17 now. Feel free to close this issue if it is complete. |
Nice, thanks |
It looks like trunk doesn't support installing extensions on Posgtres 17 yet.
Running the official postgres:17 image in Docker, I get:
The text was updated successfully, but these errors were encountered: