From 245dff7a5ab7141a4a1224eff61e2d8082493dd8 Mon Sep 17 00:00:00 2001 From: Marius Kittler Date: Thu, 1 Jun 2023 18:07:27 +0200 Subject: [PATCH] Reference further documentation for database migrations * Reference sections explaining how to import production data and how to tackle performance problems as both are very relevant when creating database migrations * Related ticket: https://progress.opensuse.org/issues/112946 --- docs/Contributing.asciidoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/Contributing.asciidoc b/docs/Contributing.asciidoc index 21a718c954eb..70131c5d5819 100644 --- a/docs/Contributing.asciidoc +++ b/docs/Contributing.asciidoc @@ -481,6 +481,16 @@ createdb -O ownername -T originaldb newdb To initialize or update the database manually before restarting the web UI you can run either `./script/initdb --init_database` or `./script/upgradedb --upgrade_database`. +Migrations that affect possibly big tables should be tested against a production +database to see how much time they need. Checkout the +<> section +for details. + +A migration can cause the analyser to regress so it produces worse query plans leading +to impaired performance. Checkout the +<> +section for how to tackle this problem. + === How to add fixtures to the database Note: This section is not about the fixtures for the testsuite. Those are located