My PostgreSQL database is unreadable or corrupt, and I need to restore it to a usable state. Will SecureRecovery for PostgreSQL help?
SecureRecovery for PostgreSQL is capable of recovering many damaged and corrupted databases, including some files with severe damage. Because the program is designed specifically for PostgreSQL, it is an effective way to restore essential data in a safe and secure manner.
To find out whether SecureRecovery for PostgreSQL will work for your database, you should try running the free demo.
What license options are available, and why should I choose one option over the others?
While the Standard license is appropriate for most users, you may need one of the other options. Visit our Licensing page to read about the differences between the software versions.
Should I back up my damaged PostgreSQL databases before running this software?
Yes, we highly recommend this as a first step. By backing up the data, you protect against user error, operating system issues and other unexpected circumstances that could damage the database during the recovery.
What are the advantages and disadvantages of the free demo version of SecureRecovery for PostgreSQL?
The main advantage of the demo is that it allows you to determine whether SecureRecovery for PostgreSQL will work for your databases before you pay for a license. It is virtually identical to the full-featured version, but it is only capable of recovering a limited number of rows.
When SecureRecovery for PostgreSQL exceeds its limits, it will populate the remaining recoverable cells with blank entries. You can then review the sample recovery and decide whether to purchase the complete software. None of the commercial versions have limits on the number of recoverable rows.
I successfully ran the application, and I can now see a new folder with SQL scripts and a batch file. What is the correct method for importing this data?
There are two ways to import the data. You can either process the SQL scripts manually or use the batch file (stored in the same directory as the recovered SQL scripts).
If you process the scripts manually, begin with the file named schema.sql, then proceed to dataNNNN.sql. The batch file automates the process and provides a simpler experience for end users.
Can I create my own batch files to run SecureRecovery for PostgreSQL through the command line?
This is an option if you have either the Enterprise license or the Service license. The Standard license is more restricted and does not allow access through the command line. Back up your files before attempting recovery and be sure to create a directory for the recovered databases.
Use this command line call: pgr.exe “”
To input patterns, use ‘?’ for a single symbol and ‘*’ for multiple symbols.