Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 127
    • Merge requests 127
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Repository

Switch branch/tag
  • slapos
  • software
  • gitlab
  • gitlab-unicorn-startup.in
Find file BlameHistoryPermalink
  • Kirill Smelkov's avatar
    gitlab/gitlab-unicorn-startup: Make sure pg_trgm extension is enabled for gitlab db · b7166b9e
    Kirill Smelkov authored Apr 12, 2016
    Starting from GitLab 8.6 pg_trgm extension becomes hard dependency of
    gitlab.
    
        https://gitlab.com/gitlab-org/gitlab-ce/commit/d24ee2a2
    
    The extension can be activated only by db superuser, so gitlab db
    migration scripts does not activate it - it has to be done by DB
    administrator or is handled by integrating code in omnibus case.
    
    As we already handle DB setup and migrations in unicorn startup script,
    as pre-action there, let's activate pg_trgm.
    b7166b9e

Replace gitlab-unicorn-startup.in

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7