Skip to content
Snippets Groups Projects
Commit da166f67 authored by Jose Torres's avatar Jose Torres
Browse files

Adding pg_trgm fix to common installation problems.

parent 8fd48955
No related branches found
No related tags found
No related merge requests found
......@@ -364,6 +364,41 @@
of GitLab and the proxy headers set in package by default are incorrect
for your environment.
### Extension missing pg_trgm
When upgrading to GitLab 8.6 PostgreSQL requires the `pg_trgm` extension. While it should be handled by the upgrade
process you might encounter a migration error which also displays a 500 server error. Its worth noting that it usually
happens on instances that have external database connections.
To fix this issue you'll need access to `psql` as superuser. Then you can install the extension and run migrations
again.
```
# Access as superuser
sudo -u gitlab-psql /opt/gitlab/embedded/bin/psql -h /var/opt/gitlab/postgresql -d gitlabhq_production
# Add extension
CREATE EXTENSION pg_trgm;
# Exit psql
\q
# Now run migrations again
sudo gitlab-rake db:migrate
```
If using Docker you first need to access your container then run the commands above and finally restart the container.
```
# Access Container
docker exec -it gitlab bash
# Run commands above
# Restart container
docker restart gitlab
```
See [Change the default proxy headers section of nginx doc][] for details on
how to override the default headers.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment