Prowess Data Unloader Complete Manual

PDU recovers PostgreSQL 10–18 data. This documentation is organized by failure type and includes command and parameter references.

Scope

PostgreSQL 10–18

EL 7/8/9 · Ubuntu · Debian

Linux x86 / ARM64

Offline file analysis

Before recovery, copy PGDATA, tablespaces, WAL, and logs. Do not continue writing to the original media.

Common entry points

Recovery scenariosChoose a guide by instance, file, or accidental operation.Usage GuideReview configuration, execution order, and outputs.ReferenceFind commands, parameters, supported types, and frequently asked questions.

Recovery scenarios

Confirm the current database state, then select the matching procedure.

File recovery

Database files and directories

The instance is unavailable, or damaged pages must be bypassed for direct file parsing.

Recover from Corrupted InstanceThe instance or system catalogs are damaged and PostgreSQL cannot start.MaterialPGDATAtable structureOutputexported dataRecover from Corrupted Data FileA relation, data page, or TOAST file is corrupted.Materialrelation filetable structureOutputexported dataRecover Single Database DirectoryOnly one database directory remains and relation files must be identified again.Materialdatabase directoryDDLOutputexported data

WAL recovery

Accidental DELETE and UPDATE

The database remains available and WAL covering the incident time range has been preserved.

Recover Deleted RecordsParse DELETE records from the relevant WAL time range.MaterialWALOutputreload dataRecover Updated RecordsRestore the before-image of one or more incorrectly updated columns.MaterialWALOutputrecovery SQL

Media recovery

Dropped and truncated tables

The table was dropped or truncated and no directly restorable backup is available.

Recover Dropped Tables Without BackupLocate residual data pages that have not been overwritten in a disk image.Materialdisk imageDDLOutputresidual pages

File and Page Identification

Unknown Files and Page Images

Choose recovery paths from surviving relation files, page images and schema evidence.

Identify Unknown Data FilesUse Probe and ProbeBatch to identify candidate table definitions, then export with confirmed mappings.Materialrelation filestab.configOutputCandidates and CSVRecover Data from a Page ImageUse PDUPlan and RecoverISO to recover data from a PDU page image.MaterialpgisoDDL / PDUPlanOutputData and unresolved dependenciesRecover Data from Disk FragmentsPreserve surviving pages and distinguish file identification, image recovery, historical layouts and attribution evidence.MaterialimagedefinitionsOutputPages and interpretation evidence

Basic workflow

Preserve the original files, identify the problem, then carry out recovery on copies.

  1. 1

    Preserve recovery materials

    Copy PGDATA, tablespaces, WAL, and logs, and record the PostgreSQL version.

  2. 2

    Identify the failure type

    Separate instance damage, file damage, accidental DML, and dropped tables.

  3. 3

    Recover from a copy

    Choose the matching commands and record the export counts, parsing failures and recovery results reported by PDU.

Reference

Find command syntax, parameter purpose, and version differences.

Command ReferenceSyntax and output descriptionsParameter ReferencePurpose and applicable conditionsSupported Data TypesEdition and PostgreSQL version differencesFrequently Asked QuestionsAnswers to common recovery questions

Supported Data Types

Numericsmallint, integer, bigint, numeric, real, double precision, money
Text and binarychar, varchar, text, name, bytea
Date and timedate, time, timestamp, timestamptz, interval
Documents and identifiersjson, jsonb, jsonpath, xml, uuid
Network and systeminet, cidr, macaddr, oid, xid, tid
Advanced typesenum, domain, tsvector, range, multirange, pgvector vector
Professional and Enterprisearrays, PostGIS geometry / geography / raster
PostgreSQL 文档