Greenplum Data warehouse can manage billions of data, but it doesn’t mean that user can generate or UPDATE random data set.Periodically, The Greenplum DBA should check the size of database schemas and their appropriate usage.Keep in mind that the size reported here includes the sizes of tables, indexes, and other objects within each schema. If we need more granular information, we can modify the query accordingly to focus on specific types of objects or individual tables.
Option 1:
select * from gp_toolkit.gp_size_of_schema_disk;
Option 2:
select schemaname, round(sum(pg_total_relation_size(schemaname||’.’||tablename))) SchemaSize from pg_tables group by 1;
Option 3:
SELECT schema_name,pg_size_pretty(sum(table_size)::bigint)
FROM
(
SELECT pg_catalog.pg_namespace.nspname as schema_name,
pg_relation_size(pg_catalog.pg_class.oid) as table_size
FROM pg_catalog.pg_class
JOIN pg_catalog.pg_namespace ON relnamespace = pg_catalog.pg_namespace.oid
) t
GROUP BY
ORDER BY ;
Option 4:
SELECT nspname AS schema_name, pg_size_pretty(pg_total_relation_size(nspname::regnamespace)) AS total_schema_size FROM pg_namespace WHERE nspname NOT IN (‘information_schema’, ‘pg_catalog’) ORDER BY total_schema_size DESC;
this query in your Greenplum database to obtain an overview of the sizes of all schemas, ordered from largest to smallest