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 PostgreSQL 17 #48495

Closed
wrenix opened this issue Oct 1, 2024 · 7 comments · Fixed by #49240
Closed

Support PostgreSQL 17 #48495

wrenix opened this issue Oct 1, 2024 · 7 comments · Fixed by #49240
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement

Comments

@wrenix
Copy link

wrenix commented Oct 1, 2024

Current i got a Warning:

PostgreSQL version "17.0" detected. PostgreSQL >=12 and <=16 is suggested for best performance, stability and functionality with this version of Nextcloud.

@wrenix wrenix added 0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement labels Oct 1, 2024
@LM-vb
Copy link

LM-vb commented Oct 7, 2024

Do you see any negative effects on your NC instance when running PostgreSQL 17?

@wrenix
Copy link
Author

wrenix commented Oct 10, 2024

Current, just this warning 😅

@js-d-coder
Copy link

I am running Nextcloud 30 and have used v29 on Postgresql 17, I did not face any issue.

@JustArchi
Copy link

JustArchi commented Oct 17, 2024

No issues observed on PostgreSQL 17 on my setup either. v29 and v30 (now).

@chrissi55
Copy link

chrissi55 commented Oct 19, 2024

upgraded the 16 main cluster to 17 and made some adjustments following several performance settings from here:

https://pgtune.leopard.in.ua/#/

Running fast and good as far as i have observed at the moment.

@GreyXor
Copy link

GreyXor commented Oct 25, 2024

same here, no issues on my nextcloud 30 + pg17

@fenvarien
Copy link

No issues with Nextcloud 30.0.2 and PostgreSQL 17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants