You might see an issue where gpbackup 1.29.0 is ran for 2hrs or more on GPDB 6.25.1 after initiating a --meta-data only backup. This issue is caused by the following section from the query.
WITH table_cte AS (SELECT DISTINCT cl.relname FROM pg_class cl INNER JOIN pg_partitions pts ON cl.relname = pts.partitiontablename AND cl.relname != pts.tablename WHERE cl.relkind IN ('r', 'f')) SELECT ic.relname AS origname, rc.relname || SUBSTRING(ic.relname, LENGTH(ch.relname)+1, LENGTH(ch.relname)) AS newname FROM pg_index i JOIN pg_class ic ON i.indexrelid = ic.oid JOIN pg_class rc ON i.indrelid = rc.oid AND rc.relname != SUBSTRING(ic.relname, 1, LENGTH(rc.relname)) JOIN pg_namespace n ON rc.relnamespace = n.oid INNER JOIN table_cte ch ON SUBSTRING(ic.relname, 1, LENGTH(ch.relname)) = ch.relname AND rc.relname != ch.relname WHERE n.nspname NOT LIKE 'pg_temp_%' AND n.nspname NOT LIKE 'pg_toast%' AND n.nspname NOT IN ('gp_toolkit', 'information_schema', 'pg_aoseg', 'pg_bitmapindex', 'pg_catalog') ;
Product Version: 6.25
To resolve the issue, gpbackup version 1.29.0 will need to (recommended)upgrade to gpbackup 1.30.0 OR downgrade to gpbackup 1.26.0.