Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

migration_style_guide.md

  • Mayra Cabrera's avatar
    9d5ea420
    Migrations guide: use atomic steps, when possible · 9d5ea420
    Mayra Cabrera authored and Evan Read's avatar Evan Read committed
    Currently, the DB migrations guide says that "you must" use non-blocking
    operations (such as CREATE INDEX CONCURRENTLY), always.
    
    But this does not make sense in cases of empty tables and leads to
    splitting the work to multiple non-atomic
    (with disable_ddl_transaction!) DB migrations.
    
    To follow KISS principle, to have fewer DB migrations steps,
    to have them atomic when it's possible and simplify deployment
    and troubleshooting, the following exceptions were added
    to the doc:
    
    - index creation,
    - index dropping,
    - defining an FK,
    - adding a column with DEFAULT,
    9d5ea420
    History
    Migrations guide: use atomic steps, when possible
    Mayra Cabrera authored and Evan Read's avatar Evan Read committed
    Currently, the DB migrations guide says that "you must" use non-blocking
    operations (such as CREATE INDEX CONCURRENTLY), always.
    
    But this does not make sense in cases of empty tables and leads to
    splitting the work to multiple non-atomic
    (with disable_ddl_transaction!) DB migrations.
    
    To follow KISS principle, to have fewer DB migrations steps,
    to have them atomic when it's possible and simplify deployment
    and troubleshooting, the following exceptions were added
    to the doc:
    
    - index creation,
    - index dropping,
    - defining an FK,
    - adding a column with DEFAULT,