sameersbn / sameersbn/docker-gitlab
postgresql Error tuple concurrently updated
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
On my server use sameersbn/gitlab:latest and sameersbn/postgresql:9.4-24
When I try to server gitlab-server I got this message
gitlab_1 | Initializing logdir...
gitlab_1 | Initializing datadir...
gitlab_1 | Updating CA certificates...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ‣ Loading pg_trgm extension...
postgresql_1 | ‣ Granting access to gitlab user...
postgresql_1 | ERROR: tuple concurrently updated
gitlab_1 | Installing configuration templates...
gitlab_1 | Configuring gitlab...
gitlabdocker_postgresql_1 exited with code 1
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ‣ Loading pg_trgm extension...
postgresql_1 | ‣ Granting access to gitlab user...
postgresql_1 | ERROR: tuple concurrently updated
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ‣ Loading pg_trgm extension...
postgresql_1 | ‣ Granting access to gitlab user...
postgresql_1 | ERROR: tuple concurrently updated
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
Reproduce the startup sequence with sameersbn/gitlab:latest and sameersbn/postgresql:9.4-24, then inspect the PostgreSQL initialization logs around loading pg_trgm and granting access to the gitlab user. Done means the database container completes initialization without the “tuple concurrently updated” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- database, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100