sameersbn / sameersbn/docker-gitlab
application_settings does not exist
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
postgresql_1 | 2024-12-03 13:53:36.348 UTC [95] ERROR: relation "application_settings" does not exist at character 491
postgresql_1 | 2024-12-03 13:53:36.348 UTC [95] STATEMENT: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
postgresql_1 | pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
postgresql_1 | c.collname, col_description(a.attrelid, a.attnum) AS comment,
postgresql_1 | attgenerated as attgenerated
postgresql_1 | FROM pg_attribute a
postgresql_1 | LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
postgresql_1 | LEFT JOIN pg_type t ON a.atttypid = t.oid
postgresql_1 | LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
postgresql_1 | WHERE a.attrelid = '"application_settings"'::regclass
postgresql_1 | AND a.attnum > 0 AND NOT a.attisdropped
postgresql_1 | ORDER BY a.attnum
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 the PostgreSQL error in the issue and inspect the docker-gitlab setup and database initialization or migration entry points for the missing application_settings relation. Reproduce the startup path, identify why the relation is absent, and confirm that the GitLab container starts without this PostgreSQL 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
- 20/100