As of yesterday OmniPITR got following changes/fixes: Fixed bug which caused immediate finish request be treated the same as smart finish request. Fixed problem with using omnipitr-backup-slave on PostgreSQL 9.0 slave, which is using streaming replication. Added option to omnipitr-restore, so that you ...

On 23rd of January, Magnus Hagander committed patch which adds: Add pg_basebackup tool for streaming base backups   This tool makes it possible to do the pg_start_backup/ copy files/pg_stop_backup step in a single command.   There are still some steps to be done before this is ...

Well, the biggest information is that hot-backups on slave work. And they work fine. Really fine. Some more information (with nice graph!):

Question from title sounds weird to you? It's just a 'rm backup_filename'? Well. I really wish it was so simple in some cases. One of the servers I'm looking into, there is interesting situation: quite busy database server (2k tps is the ...

On 2nd of February Andrew Dunstan committed his patch (with editing by Tom Lane) that: Log Message: ----------- Provide for parallel restoration from a custom format archive. Each data and post-data step is run in a separate worker child (a thread on Windows, a ...