-
Notifications
You must be signed in to change notification settings - Fork 11
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
PostgreSQL 17 #315
Comments
Thank you for this suggestion @ur5us, and indeed sounds like great benefits of PG17! We are on track to deliver PG17 in Q1 2025. Stay tuned. |
Would love to see this one land earlier than the typical EOQ1/Q2, there seem to be such notable improvements to queries (namely, the |
Thank you for your input @jeffbax ! |
Is there any update on the timeline for PG17? Were you able to expedite to Q1 @jbrown-heroku? |
Hi, is there any update on the timeline for PG17, looking forward for using it. |
Thank you for your patience! Update: We are on track for delivery targeting March-April. |
Required Terms
What service(s) is this request for?
Postgres
Tell us about what you're trying to solve. What challenges are you facing?
Improve performance for (Rails) apps by leveraging “performance of queries with IN clauses that use B-tree indexes”, faster
VACUUM
, s. https://www.postgresql.org/about/news/postgresql-17-released-2936/The text was updated successfully, but these errors were encountered: