sameersbn / sameersbn/docker-gitlab
A bug that is related to the version of PostgreSQL
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi, I'm using the docker-comse.yml file of version15.11.5 to run a gitlab server on my computer.
I encountered the this bug on my gitlab server recently.
FATAL: the database system is in recovery mode
LOG: server process (PID 10611) was terminated by signal 11: Segmentation fault
DETAIL: Failed process was running: /*application:sidekiq,correlation_id:<ID>,jid:<JID>,endpoint_id:LooseForeignKeys::CleanupWorker,db_config_name:main*/ DELETE FROM "ci_pipelines" WHERE ("ci_pipelines"."id") IN (SELECT "ci_pipelines"."id" FROM "ci_pipelines" WHERE "ci_pipelines"."merge_request_id" IN (12345, 12346) LIMIT 1000 FOR UPDATE SKIP LOCKED)
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at <TIME>
LOG: database system was not properly shut down; automatic recovery in progress
The article says that in order to fix this bug, we have to upgrade PostgreSQL to 12.7 or 13.3.
The fix is to upgrade to the latest patch level of PostgreSQL - minimum 12.7 or 13.3, but to avoid any other known bugs, select the latest patch level of your current major release (12.x or 13.x)
Can you upgrade the version of sameersbn/postgresql docker image in docker-compose.yml? The latest version of sameersbn/postgresql:12-20200524 is psql (PostgreSQL) 12.3 (Ubuntu 12.3-1.pgdg18.04+1), which is older than 12.7.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-compose.yml and inspect the sameersbn/postgresql:12-20200524 image currently used. Compare its PostgreSQL 12.3 version with the requested minimum 12.7 or later patch level, then verify that the compose configuration uses a compatible image; done means the configured image is no longer below the stated minimum.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100