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

A bug that is related to the version of PostgreSQL #2802

Open
lyenliang opened this issue Jul 19, 2023 · 5 comments
Open

A bug that is related to the version of PostgreSQL #2802

lyenliang opened this issue Jul 19, 2023 · 5 comments

Comments

@lyenliang
Copy link

lyenliang commented Jul 19, 2023

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.

@nehemiascr
Copy link

I have also been seeing the warning in the admin page

Database 'ci' is using PostgreSQL 12.3, but this version of GitLab requires PostgreSQL 13. Please upgrade your environment to a supported PostgreSQL version. See database requirements for details.

gitlab-16-1-warning-admin-page

I hope the database can be updated soon 👌

@ghost
Copy link

ghost commented Jul 20, 2023

Anyone know what the tentative date is for upgrading the postgres database to 15+? The docker compose file still uses postgres 12. My instance is just peg-legging along.

@alexbog8
Copy link

Hi,

Use sameersbn/postgresql:latest in your docker-comppose.yml file. Be sure to have a backup of the database in case you need to restore it.

@victorelec14
Copy link

Related #2771 #2572

@peterwillcn
Copy link

Why not use the official version of PostgreSQL 13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants