External PostgreSQL - Segmentation fault citing LooseForeignKeys::CleanupWorker causes complete database restart

[yserkann]

We use both sameersbn/gitlab and sameersbn/docker-postgresql Images in our self hosted Gitlab. After upgrading to Gitlab v15.3.1, we started getting the error message "External PostgreSQL - Segmentation fault citing LooseForeignKeys::CleanupWorker causes complete database restart" and the Postgresql Server started boot looping every minute. The error message was the same, which is described on gitlab.com here

The reason was the Postgresql Version that is used in the image, which is 12.3, but according to the fix described on the above gitlab.com page, it should have been minimum 12.7 or higher. And because of our current setup, we didn't want to use official Postgresql Docker image. Therefore we had to create our own Image by using sameersbn/docker-postgresql Repo, iot upgrade Postgresql to 12.12 (the latest version of 12). When we created the image to test without changing anything, the image pulled the latest version of Postgresql automatically, so we could get 12.12 in our docker Image! The error messages did not show up again and our gitlab Docker instance started as expected.

So, @sameersbn , if you can simply release your image again, by creating a new one without changing anything, we will have an up-to-date docker-postgresql Image and it will function as expected.

If this repo is not maintained anymore and a new version is not released, to anybody having the same issue: Just clone the repo locally and create the image yourself, without changing anything. It will automatically pull the postgresql 12.12 automatically and you will be good to go!