Provide different patch files for the panda_db schema changes and the postgres schema changes for scheduling cron jobs. Thanks to Xin!

Author: EdwardKaravakis

schema/postgres/sqls/patches/0.0.30.README.md

@@ -0,0 +1,37 @@
+# PanDA Database Schema Patch 0.0.30
+
+**Version:** 0.0.30  
+**Upgrade from:** 0.0.29  
+**Date:** November 2025
+
+## Overview
+
+This patch includes updates to worker node metrics tracking, JEDI task error logging, and CPU benchmarking capabilities.
+
+**⚠️ IMPORTANT VERSION FORMAT CHANGE:**  
+Starting with version 0.0.30, the `pandadb_version` table format has changed from two components (JEDI, SERVER) to a single unified component (PanDA). This is an **intentional breaking change** to reflect that PanDA Server and JEDI are always upgraded together and must be at the same schema version.
+
+**Before (0.0.29 and earlier):**
+```sql
+ component | major | minor | patch
+-----------+-------+-------+-------
+ JEDI      |     0 |     0 |    29
+ SERVER    |     0 |     0 |    29
+(2 rows)
+```
+
+**After (0.0.30 and later):**
+```sql
+ component | major | minor | patch
+-----------+-------+-------+-------
+ PanDA     |     0 |     0 |    30
+(1 row)
+```
+
+This change aligns with the SchemaChecker scripts in PanDA Server and JEDI that expect a single 'PanDA' component. 
+
+## Files in this Patch
+
+1. **0.0.30.patch.sql** - Main database updates (run against `panda_db` database)
+2. **0.0.30.cron.patch.sql** - Cron job updates (run against database where `pg_cron` extension is installed)
+3. **0.0.30.README.md** - This documentation file

schema/postgres/sqls/patches/0.0.30.cron.patch.sql

@@ -0,0 +1,20 @@
+-- Cron job updates for patch 0.0.30
+-- This file contains cron-specific updates and must be run against the database where pg_cron is installed
+--
+-- IMPORTANT: pg_cron location varies by installation:
+-- Some installations have it in 'postgres' database, others may be in the 'panda_db' database
+--
+-- To check where pg_cron is installed:
+--   SELECT extname FROM pg_extension WHERE extname = 'pg_cron';
+--
+-- Run this file against the correct database:
+--   psql -U postgres -d postgres -f 0.0.30.cron.patch.sql    (if pg_cron is in postgres)
+--   psql -U postgres -d panda_db -f 0.0.30.cron.patch.sql    (if pg_cron is in panda_db)
+--
+-- Regular database updates are in 0.0.30.patch.sql
+
+-- Drop the old cron schedule for the obsolete update_worker_node_map procedure
+-- This procedure has been replaced by update_worker_node_metrics
+SELECT cron.unschedule(
+    (SELECT jobid FROM cron.job WHERE command = 'CALL doma_panda.update_worker_node_map()')
+);

schema/postgres/sqls/patches/0.0.30.patch.sql

@@ -1,4 +1,7 @@
 -- patch to be used to upgrade from version 0.0.29
+-- This file contains regular table and procedure updates for panda_db database
+-- For cron job updates, see 0.0.30.cron.patch.sql
+
 BEGIN;
 
 DROP VIEW doma_pandabigmon.jedi_tasks_ordered;
@@ -146,12 +149,6 @@ $$;
 
 ALTER PROCEDURE doma_panda.update_worker_node_metrics() OWNER TO panda;
 
--- Drop the old cron schedule
-SELECT cron.unschedule(
-    (SELECT jobid FROM cron.job WHERE command = 'CALL doma_panda.update_worker_node_map()')
-);
-
-
 -- Add columns
 ALTER TABLE doma_panda.worker_node
   ADD COLUMN cpu_model_normalized VARCHAR(128);
@@ -172,4 +169,4 @@ TRUNCATE TABLE doma_panda.pandadb_version;
 
 INSERT INTO doma_panda.pandadb_version (component, major, minor, patch)
 VALUES ('PanDA', 0, 0, 30);
-commit;
+COMMIT;