Removes tmp_index_project_statistics_updated_at from project statistics
Compare changes
There are no changes yet
No changes between version 2 and version 1
Removes tmp_index_project_statistics_updated_at from project statistics.
It is a temporary index that was removed async in !154410 (diffs) over a week ago last week
main: == [advisory_lock_connection] object_id: 88780, pg_backend_pid: 77581
main: == 20240611103909 RemoveTmpIndexProjectStatisticsUpdatedAtSync: migrating =====
main: -- transaction_open?(nil)
main: -> 0.0000s
main: -- view_exists?(:postgres_partitions)
main: -> 0.0131s
main: -- indexes(:project_statistics)
main: -> 0.0079s
main: -- current_schema(nil)
main: -> 0.0002s
main: == 20240611103909 RemoveTmpIndexProjectStatisticsUpdatedAtSync: migrated (0.0437s)
main: == [advisory_lock_connection] object_id: 88780, pg_backend_pid: 77581
bin/rails db:migrate:down:main VERSION=20240611103909
main: == [advisory_lock_connection] object_id: 88320, pg_backend_pid: 84570
main: == 20240611103909 RemoveTmpIndexProjectStatisticsUpdatedAtSync: reverting =====
main: -- transaction_open?(nil)
main: -> 0.0000s
main: -- view_exists?(:postgres_partitions)
main: -> 0.0119s
main: -- index_exists?(:project_statistics, [:project_id, :updated_at], {:name=>"tmp_index_project_statistics_updated_at", :where=>"repository_size > 0", :algorithm=>:concurrently})
main: -> 0.0114s
main: -- execute("SET statement_timeout TO 0")
main: -> 0.0002s
main: -- add_index(:project_statistics, [:project_id, :updated_at], {:name=>"tmp_index_project_statistics_updated_at", :where=>"repository_size > 0", :algorithm=>:concurrently})
main: -> 0.0111s
main: -- execute("RESET statement_timeout")
main: -> 0.0002s
main: == 20240611103909 RemoveTmpIndexProjectStatisticsUpdatedAtSync: reverted (0.0681s)
Refs #464566 (closed)
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
Numbered steps to set up and validate the change are strongly suggested.
No changes between version 2 and version 1