Resolve "Remove geo_lfs_object_deleted_events table"
What does this MR do and why?
It removes geo_lfs_object_deleted_events
table since LFS is handled by SSF now: !62039 (diffs)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Output
Up
== 20220526042017 RemoveGeoLfsObjectDeletedEventReferences: migrating =========
-- transaction_open?()
-> 0.0000s
-- remove_column(:geo_event_log, :lfs_object_deleted_event_id, :bigint)
-> 0.0008s
== 20220526042017 RemoveGeoLfsObjectDeletedEventReferences: migrated (0.0085s)
== 20220526044516 RemoveGeoLfsObjectDeletedEventsTable: migrating =============
-- drop_table(:geo_lfs_object_deleted_events)
-> 0.0049s
== 20220526044516 RemoveGeoLfsObjectDeletedEventsTable: migrated (0.0050s) ====
Down
== 20220526044516 RemoveGeoLfsObjectDeletedEventsTable: reverting =============
-- create_table(:geo_lfs_object_deleted_events, {:id=>:bigserial})
-> 0.0038s
== 20220526044516 RemoveGeoLfsObjectDeletedEventsTable: reverted (0.0046s) ====
== 20220526042017 RemoveGeoLfsObjectDeletedEventReferences: reverting =========
-- transaction_open?()
-> 0.0000s
-- column_exists?(:geo_event_log, :lfs_object_deleted_event_id)
-> 0.0027s
-- add_column(:geo_event_log, :lfs_object_deleted_event_id, :bigint)
-> 0.0004s
-- transaction_open?()
-> 0.0000s
-- foreign_keys(:geo_event_log)
-> 0.0019s
-- transaction_open?()
-> 0.0000s
-- execute("ALTER TABLE geo_event_log\nADD CONSTRAINT fk_d5af95fcd9\nFOREIGN KEY (lfs_object_deleted_event_id)\nREFERENCES geo_lfs_object_deleted_events (id)\nON DELETE CASCADE\nNOT VALID;\n")
-> 0.0005s
-- execute("SET statement_timeout TO 0")
-> 0.0001s
-- execute("ALTER TABLE geo_event_log VALIDATE CONSTRAINT fk_d5af95fcd9;")
-> 0.0009s
-- execute("RESET statement_timeout")
-> 0.0002s
-- transaction_open?()
-> 0.0000s
-- index_exists?(:geo_event_log, :lfs_object_deleted_event_id, {:name=>"index_geo_event_log_on_lfs_object_deleted_event_id", :where=>"(lfs_object_deleted_event_id IS NOT NULL)", :algorithm=>:concurrently})
-> 0.0029s
-- add_index(:geo_event_log, :lfs_object_deleted_event_id, {:name=>"index_geo_event_log_on_lfs_object_deleted_event_id", :where=>"(lfs_object_deleted_event_id IS NOT NULL)", :algorithm=>:concurrently})
-> 0.0007s
== 20220526042017 RemoveGeoLfsObjectDeletedEventReferences: reverted (0.0194s)
gitlabhq_development=# \d geo_lfs_object_deleted_events
Table "public.geo_lfs_object_deleted_events"
Column | Type | Collation | Nullable | Default
---------------+-------------------+-----------+----------+-----------------------------------------------------------
id | bigint | | not null | nextval('geo_lfs_object_deleted_events_id_seq'::regclass)
lfs_object_id | integer | | not null |
oid | character varying | | not null |
file_path | character varying | | not null |
Indexes:
"geo_lfs_object_deleted_events_pkey" PRIMARY KEY, btree (id)
"index_geo_lfs_object_deleted_events_on_lfs_object_id" btree (lfs_object_id)
Referenced by:
TABLE "geo_event_log" CONSTRAINT "fk_d5af95fcd9" FOREIGN KEY (lfs_object_deleted_event_id) REFERENCES geo_lfs_object_deleted_events(id) ON DELETE CASCADE
Related to #362843 (closed)
Edited by Javiera Tapia