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
Just released version 0.3.0 of our tool for handling WAL based replication in PostgreSQL - OmniPITR. Version jump is related to addition of another tool - omnipitr-synch. This tool is used to copy PostgreSQL data dir (including all tablespaces of course) ...
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 ...
On 6th of March, Simon Riggs committed patch: Efficient transaction-controlled synchronous replication. If a standby is broadcasting reply messages and we have named one or more standbys in synchronous_standby_names then allow users who set synchronous_replication to wait for commit, which then provides strict data integrity ...
On 16th of February, , Robert Haas committed patch: pg_ctl promote Fujii Masao, reviewed by Robert Haas, Stephen Frost, and Magnus Hagander.
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 ...
On 7th of January (I know, it was quite some time ago, I apologize for delay) Itagaki Takahiro committed patch: New system view pg_stat_replication displays activity of wal sender processes. Itagaki Takahiro and Simon Riggs.
Well, the biggest information is that hot-backups on slave work. And they work fine. Really fine. Some more information (with nice graph!):
There are several approaches on replication/failover - you might have heard of Slony, Londiste, pgPool and some other tools. WAL Replication is different from all of them in one aspect - it doesn't let you query slave database (until 9.0, in ...
