Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Architectural Logic**: Metadata drives optimization and discovery; system catalogs are the source of truth. **Storage**: pg_catalog (PostgreSQL), information_schema (standard). Tables: pg_class (tables, indexes), pg_attribute (columns), pg_index. **Access**: `SELECT * FROM...
Architectural Logic: Metadata drives optimization and discovery; system catalogs are the source of truth. Storage: pg_catalog (PostgreSQL), information_schema (standard). Tables: pg_class (tables, indexes), pg_attribute (columns), pg_index. Access: SELECT * FROM information_schema.tables WHERE table_schema='public'. Why It Matters: Optimizer uses statistics for plans; tools use for discovery and lineage. Scalability: Maintain statistics (ANALYZE); extended properties for custom metadata. Warehouses: Snowflake (information_schema, account_usage); BigQuery (information_schema). Best practice: Use INFORMATION_SCHEMA for portability; document custom metadata.
Red Flag: Ignoring statistics—query plans degrade. Pro-Move: Mention ANALYZE strategy; using system tables for data catalog or lineage; governance integration.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.