Don't use cascading deletes in Citus 11 migration script (#5767)

Using CASCADE in a DELETE can inadvertently delete things we don't
intend to. It's safer to fail hard and make the user delete depending
things manually.
pull/5761/head
Jelte Fennema 2022-03-09 14:35:23 +01:00 committed by GitHub
parent 333bcc7948
commit c8839de68b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions

View File

@ -31,8 +31,11 @@
#include "udfs/citus_calculate_gpid/11.0-1.sql" #include "udfs/citus_calculate_gpid/11.0-1.sql"
#include "udfs/citus_backend_gpid/11.0-1.sql" #include "udfs/citus_backend_gpid/11.0-1.sql"
DROP FUNCTION IF EXISTS pg_catalog.citus_dist_stat_activity() CASCADE; DROP VIEW IF EXISTS pg_catalog.citus_lock_waits;
DROP FUNCTION IF EXISTS pg_catalog.citus_worker_stat_activity() CASCADE; DROP VIEW IF EXISTS pg_catalog.citus_dist_stat_activity;
DROP VIEW IF EXISTS pg_catalog.citus_worker_stat_activity;
DROP FUNCTION IF EXISTS pg_catalog.citus_dist_stat_activity();
DROP FUNCTION IF EXISTS pg_catalog.citus_worker_stat_activity();
#include "udfs/citus_dist_stat_activity/11.0-1.sql" #include "udfs/citus_dist_stat_activity/11.0-1.sql"
-- a very simple helper function defined for citus_lock_waits -- a very simple helper function defined for citus_lock_waits