Skip to content
Snippets Groups Projects
Commit b65dfdc8 authored by Adam Hegyi's avatar Adam Hegyi
Browse files

Merge branch 'mk-migration-guide-multidb-docs' into 'master'

Style guide: Link to multi-db migration docs

See merge request !91270
parents f2d03bff 0bc79267
No related branches found
No related tags found
1 merge request!91270Style guide: Link to multi-db migration docs
Pipeline #576622212 passed with warnings
Pipeline: GitLab

#576625309

    ......@@ -90,6 +90,14 @@ Keep in mind that all durations should be measured against GitLab.com.
    | Post-deployment migrations | `<= 10 minutes` | A valid exception are schema changes, since they must not happen in background migrations. |
    | Background migrations | `> 10 minutes` | Since these are suitable for larger tables, it's not possible to set a precise timing guideline, however, any single query must stay below [`1 second` execution time](query_performance.md#timing-guidelines-for-queries) with cold caches. |
    ## Decide which database to target
    GitLab connects to two different Postgres databases: `main` and `ci`. This split can affect migrations
    as they may run on either or both of these databases.
    Read [Migrations for Multiple databases](database/migrations_for_multiple_databases.md) to understand if or how
    a migration you add should account for this.
    ## Create a regular schema migration
    To create a migration you can use the following Rails generator:
    ......
    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