Database Group Triage for week ending 2023-09-29

About

This issue is used by groupdatabase to triage issues and make sure they get properly assigned and prioritized. Each week, a bot will look up the old issue, pick the next assignee in the list, and submit a new issue with a list of any issues that may need attention from the team.

Last week's issue

Process

• Review any issues with undefined types
• Post any questions or pressing issues to the database group meeting doc
• Post a comment on the database group status issue

  For triage this week there were 0 issues in need of triage, 4 issues without throughput labels, and 6 other database issues reviewed. <link to this issue>

Issues with Undefined Type

For each issue below:

1. Assess if the issue is appropriately assigned to groupdatabase, if not add the correct group label.
2. Add the proper work type label, or if the issue is a request for support, redirect the user to our support resources with the following message:

   Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including:
   * [Technical Support for Paid Tiers](https://about.gitlab.com/support/)
   * [Community Forum](https://forum.gitlab.com/)
   * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references)
   
   Please refer to our [Support page](https://about.gitlab.com/support/) for more information.
   
   If you believe this was closed in error, please feel free to re-open the issue.
   
   /label ~"support request"
   /close

3. If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
4. Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and @rogerwoo to help with scheduling and priority.

• Upgrade to 16.4: Migration 20230828153646 ExtendPushRulesRegexLimits fails because commit_message_negative_regex does not exist
• Add range int partitioning strategy
• Schema validation report
• error dumping the contents of table "merge_request_diff_files" failed PQgetResult failed

Recent issues labeled database

For each issue below:

1. If the issue has no group label, consider if it should be addressed by groupdatabase and if so label it.
2. If the issue has a group, and you think they may need assistance from us:
   • If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
   • Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and/or @rogerwoo

• groupproject management Timelogs GraphQL resolver authorization checks issue
• groupcode review Add performance metrics on partitioned MRD_files table
• groupcode review Analyze MRD_files queries and confirm partitioning compatibility
• groupcode review Add performance metrics on partitioned MRD_files table
• groupcode review Analyze MRD_files queries and confirm partitioning compatibility
• groupthreat insights Synchronously Validate finding_id foreign key on vulnerabilities table

@alexives if @mattkasa isn't available this week, please reassign to @praba.m7n cc @rogerwoo