PostgreSQL

DataLens migrated project data from DuckDB to PostgreSQL for enhanced concurrency, with backend interactions, data storage, and metadata management relying on PostgreSQL, supporting multilingual features, and hosting the project_14 schema with 72 tables. Extraction Worker will write extracted data to PostgreSQL schemas instead of DuckDB. After migration, Query Router will read extracted data from PostgreSQL schemas. Post-migration Arctic SQL will generate SQL queries targeting PostgreSQL with minor translation. PgDataService manages extracted project data stored in PostgreSQL schemas. Each project schema such as Project 14's schema is a distinct namespace within PostgreSQL. Text chunks for all projects are stored in a unified table in PostgreSQL's public schema. extracted_tables table tracks metadata about extracted tables per project inside PostgreSQL. Phase 2 Strategy Research & Decision Point uses PostgreSQL for file storing and metadata management as indicated by files stored in PostgreSQL during deployment tests. Backend server uses PostgreSQL for tracking file metadata, users, projects, and authentication. PostgreSQL database stores the project_14 schema used for SVGV data storage and extraction results. The Data Discovery system integrates with the PostgreSQL database for storing and retrieving data. IronClaw agent tables are physical tables mapped within the PostgreSQL database for persistent storage of agent sessions and related data. OpenClaw Skill API references PostgreSQL database for metadata of the 132 budget files. theo Backend accesses PostgreSQL database to manage budget files metadata as part of the data platform. PostgreSQL catalogs metadata for SVGV files but does not contain extracted budget tables after system restart. PostgreSQL database stores user information for authentication and project tracking. PostgreSQL database stores project metadata like org_id and created_by user.