sameersbn / sameersbn/docker-gitlab
ERROR: relation "postgres_partitions" does not exist at character 454
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've upgraded gitlab(13.4.3->13.7.1) , I got following error.
2021-01-07 16:03:58.707 JST [1] LOG: database system is ready to accept connections
2021-01-07 16:04:30.951 JST [1717] ERROR: relation "postgres_partitions" does not exist at character 454
2021-01-07 16:04:30.951 JST [1717] STATEMENT: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
c.collname, col_description(a.attrelid, a.attnum) AS comment
FROM pg_attribute a
LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
LEFT JOIN pg_type t ON a.atttypid = t.oid
LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
WHERE a.attrelid = '"postgres_partitions"'::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum
How do I fix?
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 by investigating the PostgreSQL error and the GitLab 13.4.3 to 13.7.1 upgrade context, using the logged query against postgres_partitions as the entry point. Done means identifying the migration or schema state responsible and documenting a verified remediation for affected Dockerized GitLab installations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100