Find and export
your PostgreSQL data.

1. 1Connect with a SQL client using an account allowed to inspect the databases in scope.
2. 2Run the read-only size query below and record the databases included.
3. 3For important tables, use pg_total_relation_size for table-plus-index size and inspect row counts separately.
4. 4Use the earliest relevant record timestamp to establish the retained business period.

SELECT datname, pg_database_size(datname) AS size_bytes
FROM pg_database
WHERE NOT datistemplate
ORDER BY size_bytes DESC;

Report in GB, naming databases, schemas and the measurement basis. Add principal table and record counts where useful.

Describe the oldest retained business dates, external files and backups separately. Identify the application or staff scope represented.

1. 1Have the database administrator plan a consistent export, using a suitable replica where appropriate.
2. 2Use pg_dump for each database in a supported custom, directory or SQL format.
3. 3Review pg_dumpall --globals-only when roles and other cluster-wide definitions are required.
4. 4Collect external files separately and verify the archive against the agreed databases and schema.

pg_dump exports one database; cluster-wide roles and tablespaces use a separate route.

A dump contains live data and index definitions rather than the on-disk index contents and dead rows, so its size can differ from the meter.

Application tables can preserve the events and relationships behind a business workflow.

Schema and field descriptions help connect those records to the operations they represent.

Select databases, tables and columns in scope, reviewing personal fields and confidential application data.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.