Just released new version, 0.6.0 (it should be visible on pgxn soon) of OmniPITR set of tools. New version has one new feature - parallelism. This works in omnipitr-archive and omnipitr-backup-* programs, and allows for parallel delivery to remote destinations (multiple -dr ...

Today, I released new version of OmniPITR - 0.5.0. This new version has one important new feature - which is so called "direct destination" for backups. What it means? What it does? How it helps? Let's see...

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 29th of December, Robert Haas committed interesting patch, which does: Support unlogged tables.   The contents of an unlogged table aren't WAL-logged; thus, they are not available on standby servers and are truncated whenever the database system enters recovery. Indexes on unlogged tables ...

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

I tend to write about new features in new versions of PostgreSQL, but this patch actually fixes one of the things that annoy me a lot, so here it goes: On 26th of January, Simon Riggs committed: Log Message: ----------- Fix longstanding gripe that ...

The BIG feature. The feature that made PostgreSQL leap from 8.4 to 9.0. Patch was written by Fujii Masao, and committed by Heikki Linnakangas on 15th of January 2010: Log Message: ----------- Introduce Streaming Replication.   This includes two new kinds of postmaster processes, walsenders ...