change the identity of tables to DEFAULT for 19 tables in grpd-main

Production Change

Change Summary

The goal of this change is set the replication identity to default in production main, where we have 19 tables which are with the setup to nothing.

This change will reduce any error when we have enabled logical replication to a cascade cluster.

Change Details

  1. Services Impacted - Database
  2. Change Technician - @Finotto
  3. Change Reviewer - @NikolayS
  4. Time tracking - 5 minutes
  5. Downtime Component - 0

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

  • Set label changein-progress /label ~change::in-progress
  • List the tables that will be changed:
SELECT 
   ' ALTER TABLE '||relname||' REPLICA IDENTITY DEFAULT; ' 
FROM pg_class C
LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)
WHERE 
  nspname NOT IN ('pg_catalog', 'information_schema') AND
  relkind='r' AND
  relreplident='n' ;--nothing;
  • Verify the output are 19 like the ones we will execute:
  SET lock_timeout = '1s';
  ALTER TABLE analytics_language_trend_repository_languages REPLICA IDENTITY DEFAULT;
  ALTER TABLE approval_project_rules_protected_branches REPLICA IDENTITY DEFAULT;
  ALTER TABLE deployment_merge_requests REPLICA IDENTITY DEFAULT;
  ALTER TABLE elasticsearch_indexed_namespaces REPLICA IDENTITY DEFAULT;
  ALTER TABLE elasticsearch_indexed_projects REPLICA IDENTITY DEFAULT;
  ALTER TABLE issue_assignees REPLICA IDENTITY DEFAULT;
  ALTER TABLE issues_prometheus_alert_events REPLICA IDENTITY DEFAULT;
  ALTER TABLE issues_self_managed_prometheus_alert_events REPLICA IDENTITY DEFAULT;
  ALTER TABLE merge_request_context_commit_diff_files REPLICA IDENTITY DEFAULT;
  ALTER TABLE merge_request_diff_commits REPLICA IDENTITY DEFAULT;
  ALTER TABLE merge_request_diff_files REPLICA IDENTITY DEFAULT;
  ALTER TABLE milestone_releases REPLICA IDENTITY DEFAULT;
  ALTER TABLE project_authorizations REPLICA IDENTITY DEFAULT;
  ALTER TABLE project_pages_metadata REPLICA IDENTITY DEFAULT;
  ALTER TABLE push_event_payloads REPLICA IDENTITY DEFAULT;
  ALTER TABLE repository_languages REPLICA IDENTITY DEFAULT;
  ALTER TABLE schema_migrations REPLICA IDENTITY DEFAULT;
  ALTER TABLE user_interacted_projects REPLICA IDENTITY DEFAULT;
  ALTER TABLE users_security_dashboard_projects REPLICA IDENTITY DEFAULT;

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

  • Execute the following command:
  SET lock_timeout = '1s';
  ALTER TABLE analytics_language_trend_repository_languages REPLICA IDENTITY NOTHING;
  ALTER TABLE approval_project_rules_protected_branches REPLICA IDENTITY NOTHING;
  ALTER TABLE deployment_merge_requests REPLICA IDENTITY NOTHING;
  ALTER TABLE elasticsearch_indexed_namespaces REPLICA IDENTITY NOTHING;
  ALTER TABLE elasticsearch_indexed_projects REPLICA IDENTITY NOTHING;
  ALTER TABLE issue_assignees REPLICA IDENTITY NOTHING;
  ALTER TABLE issues_prometheus_alert_events REPLICA IDENTITY NOTHING;
  ALTER TABLE issues_self_managed_prometheus_alert_events REPLICA IDENTITY NOTHING;
  ALTER TABLE merge_request_context_commit_diff_files REPLICA IDENTITY NOTHING;
  ALTER TABLE merge_request_diff_commits REPLICA IDENTITY NOTHING;
  ALTER TABLE merge_request_diff_files REPLICA IDENTITY NOTHING;
  ALTER TABLE milestone_releases REPLICA IDENTITY NOTHING;
  ALTER TABLE project_authorizations REPLICA IDENTITY NOTHING;
  ALTER TABLE project_pages_metadata REPLICA IDENTITY NOTHING;
  ALTER TABLE push_event_payloads REPLICA IDENTITY NOTHING;
  ALTER TABLE repository_languages REPLICA IDENTITY NOTHING;
  ALTER TABLE schema_migrations REPLICA IDENTITY NOTHING;
  ALTER TABLE user_interacted_projects REPLICA IDENTITY NOTHING;
  ALTER TABLE users_security_dashboard_projects REPLICA IDENTITY NOTHING;
  • Rollback Step 2
  • Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

Change Reviewer checklist

C4 C3 C2 C1:

  • Check if the following applies:
    • The scheduled day and time of execution of the change is appropriate.
    • The change plan is technically accurate.
    • The change plan includes estimated timing values based on previous testing.
    • The change plan includes a viable rollback plan.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

  • Check if the following applies:
    • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
    • The change plan includes success measures for all steps/milestones during the execution.
    • The change adequately minimizes risk within the environment/service.
    • The performance implications of executing the change are well-understood and documented.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
      • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
    • The change has a primary and secondary SRE with knowledge of the details available during the change window.
    • The labels blocks deployments and/or blocks feature-flags are applied as necessary

Change Technician checklist

  • Check if all items below are complete:
    • The change plan is technically accurate.
    • This Change Issue is linked to the appropriate Issue and/or Epic
    • Change has been tested in staging and results noted in a comment on this issue.
    • A dry-run has been conducted and results noted in a comment on this issue.
    • The change execution window respects the Production Change Lock periods.
    • For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
    • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
    • For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
    • For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
    • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
    • There are currently no active incidents that are severity1 or severity2
    • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Alexander Sosna