Upgrade to 16 ?

[th-2021]

Now that gitlab (docker-gitlab) requires Postgresql 16, can we get a new version?

[HammyHavoc]

Yes, wondering about this too.

[th-2021]

@sameersbn any chance for an update to postgresql 16?

[tomus85]

Yes, please. I have updated GitLab to version 18, and now I am seeing a warning on the admin page.

[tomus85]

Just spotted this in the readme file on the GitLab repo (https://github.com/sameersbn/docker-gitlab)

If you're using sameersbn/postgresql then please upgrade to kkimurak/sameersbn-postgresql:16 or later

[tomus85]

It worked for me, so I guess we can close this issue.

[th-2021]

This issue is open to get this repo upgraded to PG 16.
There is a PR open and there is the kkimurak fork.

What should be done is bring this repo to PG 16.

[kkimurak]

From someone who forked this repository and executing docker build / docker push weekly for a month:
I agree that this repository should be updated if possible. It's bad that so many people are unintentionally lost.

---

By the way I don't understand why opening separate issues even a pull request has already been submitted. The discussion shouldn't be scattered. It would be enough to ping the maintainer in the existing one (whether that would be effective or not).

Also, saying "same here" is just noise and doesn't move things forward.

These are just my personal opinion so feel free to ignore me. It's a common sight to see everywhere, so I understand that there are a certain number of people who don't think that way..

[HammyHavoc]

From someone who forked this repository and executing docker build / docker push weekly for a month:
I agree that this repository should be updated if possible. It's bad that so many people are unintentionally lost.

---

By the way I don't understand why opening separate issues even a pull request has already been submitted. The discussion shouldn't be scattered. It would be enough to ping the maintainer in the existing one (whether that would be effective or not).

Also, saying "same here" is just noise and doesn't move things forward.

These are just my personal opinion so feel free to ignore me. It's a common sight to see everywhere, so I understand that there are a certain number of people who don't think that way..

The "why" is easy to explain.

Most people using these images are not developers and do not understand what the best practices are in terms of using GitHub or any kind of issues function on a Git repository server.

When maintainers tell users that 'Support' is available via the GitHub Issues URL in an Unraid template then they go to places like this instead of the forums.

I agree though, the discussion shouldn't be scattered, but this is where some kind of 'issue merge' feature akin to merging pull requests would be great, but that's a platform issue rather than a social one, IMO. You can't expect people to follow best practices as non-devs.

[jstdoit]

great.