Skip to content
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

support pg16 #148

Closed
wuputah opened this issue Sep 14, 2023 · 5 comments
Closed

support pg16 #148

wuputah opened this issue Sep 14, 2023 · 5 comments
Labels
enhancement New feature or request
Milestone

Comments

@wuputah
Copy link
Member

wuputah commented Sep 14, 2023

What's wrong?

pg16 is not supported :)

@wuputah wuputah added the enhancement New feature or request label Sep 14, 2023
@wuputah wuputah added this to the 1.1.0 milestone Sep 14, 2023
@stvhanna
Copy link

stvhanna commented Sep 24, 2023

@wuputah Thanks for a great tool, what is the timeframe for supporting PG16? https://www.postgresql.org/about/news/postgresql-16-released-2715/

I'm spinning up a new server and would love to use the latest PG with Hydra

@wuputah
Copy link
Member Author

wuputah commented Sep 25, 2023

Sorry, I don't have an estimate at this time.

Personally, I recommend letting new Postgres releases bake for at least 4 months (to the .2 release, if not 7 months (to the .3 release) before adopting it for production usage. So I would recommend continuing to use PG15 at this time.

@Vonng
Copy link

Vonng commented Oct 16, 2023

Citus 12.1 support PG 16 now ;)

@muntdan
Copy link

muntdan commented Nov 9, 2023

@wuputah
Copy link
Member Author

wuputah commented Dec 8, 2023

fixed by #200

@wuputah wuputah closed this as completed Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants