coordination #109846: [epic] Ensure all our database tables accomodate enough data, e.g. bigint for ids
coordination #112961: [epic] Followup to "openqa.suse.de is not reachable anymore, response times > 30s, multiple alerts over the weekend"
Extend openQA documentation with best practices what to do after migration, e.g. look at pg_stats
We learned during #112718 that it's a good idea to look at pg_stats if there are any "slow queries", either as regression from the migration or just from other issues and we have not realized yet. We should make sure our openQA database migration guide includes best practices as well
- AC1: Our documentation reminds what to do after migration
Point to https://github.com/os-autoinst/openQA/pull/4716/files#diff-71734bf4d91118f92743c7d0db9218c4f24729410e020110884606b5ad6a3878R1201 in https://github.com/os-autoinst/openQA/blob/master/docs/Contributing.asciidoc#how-to-update-the-database-schema