On 23rd of March, Heikki Linnakangas committed patch:
Add pg_rewind, for re-synchronizing a master server after failback. Earlier versions of this tool were available (and still are) on github. Thanks to Michael Paquier, Alvaro Herrera, Peter Eisentraut, Amit Kapila, and Satoshi Nagayasu for review.
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 – setup some kind of replication and backups.
What to use, how, and why? This is what this post is all about.
Continue reading I have PostgreSQL, loaded some data, and have app using it. Now what?
On 25th of January, Simon Riggs committed patch:
Allow pg_basebackup from standby node with safety checking. Base backup follows recommended procedure, plus goes to great lengths to ensure that partial page writes are avoided. Jun Ishizuka and Fujii Masao, with minor modifications
On 19th of July, Simon Riggs committed patch:
Cascading replication feature FOR streaming log-based replication. Standby servers can now have WALSender processes, which can WORK WITH either WALReceiver OR archive_commands TO pass DATA. Fully updated docs, including NEW conceptual terms OF sending server, upstream AND downstream servers. WALSenders TERMINATED WHEN promote TO master. Fujii Masao, review, rework AND doc rewrite BY Simon Riggs
Continue reading Waiting for 9.2 – cascading streaming replication
Well, the biggest information is that hot-backups on slave work. And they work fine. Really fine.
Some more information (with nice graph!):