Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 197
    • Issues 197
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #268

Closed
Open
Created May 07, 2020 by Thomas Markwalder@tmarkDeveloper

Detect incompatible Postgresql version

During initial environment setup I inadvertently pointed Stork to Postgresql 9.5. This apparently caused a SQL syntax error in the migrations code. IIRC it had something to with "AS", syntax error at or near "AS". I did not save the exact message. Upon pointing Stork to Postgresql 11 everything was fine.

It should be possible to detect the Postgresql version in the init db or migration logic and bail if it is too old. Barring that we might consider a more helpful failure message if possible.

Assignee
Assign to
Time tracking