SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-23 22:33:39 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Immich using PostgreSQL 16, bump it to 18 #2189

New Issue
Closed
opened 2025-11-20 05:24:56 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 05:24:56 -05:00
Owner
Copy Link

Originally created by @devdecrux on GitHub (Oct 25, 2025).

📌 Task summary

Bump PostgreSQL to 18 (current version) for Immich script

📋 Task details

I just installed Immich and recognized that PostgreSQL version 16 is being used. However, if there are no limitations maybe upgrading to the latest current version would be beneficial at least from security perspective.

Originally created by @devdecrux on GitHub (Oct 25, 2025). ### 📌 Task summary Bump PostgreSQL to 18 (current version) for Immich script ### 📋 Task details I just installed Immich and recognized that PostgreSQL version 16 is being used. However, if there are no limitations maybe upgrading to the latest current version would be beneficial at least from security perspective.
saavagebueno commented 2025-11-20 05:24:57 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 25, 2025):

what security flaws v16 has?

@tremor021 commented on GitHub (Oct 25, 2025): what security flaws v16 has?
saavagebueno commented 2025-11-20 05:24:57 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 25, 2025):

@vhsdream

@michelroegl-brunner commented on GitHub (Oct 25, 2025): @vhsdream
saavagebueno commented 2025-11-20 05:24:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 25, 2025):

Upgrading only should be done by yourself. Psql is Not easy to handle and need interactive Feedback.

By the way, Microsoft / Azure uses 14. 16 is full Up2date and 18 available since 5 weeks.

@MickLesk commented on GitHub (Oct 25, 2025): Upgrading only should be done by yourself. Psql is Not easy to handle and need interactive Feedback. By the way, Microsoft / Azure uses 14. 16 is full Up2date and 18 available since 5 weeks.
saavagebueno commented 2025-11-20 05:24:57 -05:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Oct 25, 2025):

Yeah I'm only updating Immich to use latest supported Postgres when they stop supporting 16.

@vhsdream commented on GitHub (Oct 25, 2025): Yeah I'm only updating Immich to use latest supported Postgres when they stop supporting 16.
saavagebueno commented 2025-11-20 05:24:57 -05:00
Author
Owner
Copy Link

@devdecrux commented on GitHub (Oct 25, 2025):

I am not saying it's mandatory to upgrade to 18, but there are nice to have things in the newest version. Based on multiple sources https://www.sqlpassion.at/archive/2025/09/29/whats-new-in-postgresql-18/ for example:

  • Major IO performance improvement
  • Many enhanced security features, the most important from my perspective: OAuth auth
  • Better monitoring
    Of course this topic is only a suggestion and I am not saying that it's mandatory to be updated.

what security flaws v16 has?

Sorry, probably you misunderstood me but I didn't say there are security flaws tho.

@devdecrux commented on GitHub (Oct 25, 2025): I am not saying it's mandatory to upgrade to 18, but there are nice to have things in the newest version. Based on multiple sources https://www.sqlpassion.at/archive/2025/09/29/whats-new-in-postgresql-18/ for example: - Major IO performance improvement - Many enhanced security features, the most important from my perspective: OAuth auth - Better monitoring Of course this topic is only a suggestion and I am not saying that it's mandatory to be updated. > what security flaws v16 has? Sorry, probably you misunderstood me but I didn't say there are security flaws tho.
saavagebueno commented 2025-11-20 05:24:58 -05:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Oct 25, 2025):

Don't get me wrong, updating to latest Postgres will happen, it's just not a priority at the moment. And perhaps I'm just lacking imagination, but I don't see how OAuth could be used in this particular use-case; perhaps if you had a single Postgres instance running in it's own LXC with a bunch of DBs from other LXCs feeding into it, sure. But I don't see the point of using that with the way we configure the Immich LXC.

Closing this as not planned, for now.

@vhsdream commented on GitHub (Oct 25, 2025): Don't get me wrong, updating to latest Postgres will happen, it's just not a priority at the moment. And perhaps I'm just lacking imagination, but I don't see how OAuth could be used in this particular use-case; perhaps if you had a single Postgres instance running in it's own LXC with a bunch of DBs from other LXCs feeding into it, sure. But I don't see the point of using that with the way we configure the Immich LXC. Closing this as not planned, for now.
saavagebueno commented 2025-11-20 05:24:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 25, 2025):

You can bump your db by your own, you can always give feedback, how do you upgrade, and whats going on. (Issues, or all stable...)

@MickLesk commented on GitHub (Oct 25, 2025): You can bump your db by your own, you can always give feedback, how do you upgrade, and whats going on. (Issues, or all stable...)
saavagebueno commented 2025-11-20 05:24:58 -05:00
Author
Owner
Copy Link

@devdecrux commented on GitHub (Oct 25, 2025):

Thank you @vhsdream and @MickLesk. Those are legit answers! Will you keep you updated how 18 is behaving.

@devdecrux commented on GitHub (Oct 25, 2025): Thank you @vhsdream and @MickLesk. Those are legit answers! Will you keep you updated how 18 is behaving.
saavagebueno commented 2025-11-20 05:24:58 -05:00
Author
Owner
Copy Link

@Mraedis commented on GitHub (Oct 29, 2025):

FYI Immich itself will be updating to v18 in the near future so feel free to wait it out.

@Mraedis commented on GitHub (Oct 29, 2025): FYI Immich itself will be updating to v18 in the near future so feel free to wait it out.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2189
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?