Unique Advantages
PDU stands apart from other PostgreSQL recovery tools through its unique combination of simplicity, capability, and safety. Here's what makes PDU different.
Simplicity: Two Files, Complete Solution
Minimal Footprint
PDU consists of only two files:
pdu{10-18}The executable file for your PostgreSQL version
pdu.iniSimple configuration file with just 2 key settings
Compare to Traditional Approaches
- • No complex dependencies to install
- • No lengthy setup procedures
- • No compilation required
- • No database server installation needed
- • Works immediately after extraction
Unified Interface: One Tool for All Scenarios
| Scenario | Traditional Tools | PDU |
|---|---|---|
| Corrupted database | pg_filedump + manual parsing | b; → unload |
| Deleted records | pg_waldump + pg_dirtyread | scan → restore del |
| Updated records | pg_waldump + custom scripts | scan → restore upd |
| Dropped tables | No solution | dropscan |
PostgreSQL-Native Experience
PDU feels like a natural extension of psql. If you know PostgreSQL, you already know how to use PDU:
Familiar Commands
Intuitive Navigation
Non-Invasive: Read-Only Recovery
PDU Approach
- Only reads source data files
- Never modifies original files
- Outputs to separate directory
- Safe to retry multiple times
Traditional Tools Risk
- pg_resetwal may cause data loss
- Some tools modify source files
- Errors may worsen corruption
- One chance only approach
The Only Solution for DROP TABLE
The ONLY Revealed Feasible Method
When a table is dropped without a backup, traditional PostgreSQL tools offer no solution. The data files are immediately unlinked, and the metadata is removed from system catalogs.
PDU's dropscan command is currently the only publicly available method to recover data from dropped tables by scanning disk fragments for recoverable data pages.
Data Type Support
Numeric Types
Text and Binary
Date and Time
JSON, XML, and General Types
Network and Bit Strings
Other Common Types
Enterprise Edition: Adds the array types listed in Supported Data Types and PostGIS geometry, geography, and raster columns. Community Edition differences, PostgreSQL version requirements, and currently unsupported types are listed there as well. View the full list
Version Compatibility
EL 7/8/9
Ubuntu Linux
Debian Linux
Linux x86_64
Linux ARM64
Summary: Why Choose PDU
Simple
Two files, zero dependencies
Unified
One tool for all scenarios
Familiar
PostgreSQL-native experience
Safe
Read-only, non-invasive
Unique
Only DROP TABLE solution
Compatible
PostgreSQL 10-18 support