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

On 22nd of August, Alvaro Herrera committed patch: Implement ALTER TABLE .. SET LOGGED / UNLOGGED This enables changing permanent (logged) tables to unlogged and vice-versa. (Docs for ALTER TABLE / SET TABLESPACE got shuffled in an order that hopefully makes more sense than the ...

On 11th of December, Robert Haas committed patch: Add new wal_level, logical, sufficient for logical decoding. When wal_level=logical, we'll log columns from the old tuple as configured by the REPLICA IDENTITY facility added in commit 07cacba983ef79be4a84fcd0e0ca3b5fcb85dd65. This makes it possible a properly-configured logical replication ...

Just released new version of OmniPITR. This version has one important new feature: when you're calling omnipitr-backup-slave, it will make backups only of required xlog files, and not, as previously, of all in walarchive directory. This is important, especially in case you ...

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

While there are some docs on it, I decided to write about it, in perhaps more accessible language - not as a developer, but as PostgreSQL user. Some parts (quite large parts) were described in one of my earlier posts, but ...

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