On 20th of October, Robert Haas committed patch: Rename "pg_xlog" directory to "pg_wal". "xlog" is not a particularly clear abbreviation for "write-ahead log", and it sometimes confuses users into believe that the contents of the "pg_xlog" directory are not critical data, leading to unpleasant consequences. ...

One of my clients is upgrading some servers. The procedure we have took some time to get to current state, and we found some potential problems, so decided to write more about it.

I had to deal with this question, or some version of it, quite a few times. So, decided to write a summary on what one could (or should) do, after data is in database, and application is running. Namely - ...

On 25th of January, Heikki Linnakangas committed patch: Add recovery_target='immediate' option. This allows ending recovery as a consistent state has been reached. Without this, there was no easy way to e.g restore an online backup, without replaying any extra WAL after the backup ended. MauMau ...

Recently someone was looking for help with script from Pg wiki. I never really checked it, but when talking with the guy needing help, I looked at it. And didn't really like it.

Around the time that Xzilla wrote about the book, Packt contacted me and asked for a review. Since I generally don't really read technical books, I declined the offer, but Sandy from Packt was very persistent, and asked if I could ...

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 ...