Skip site navigation (1) Skip section navigation (2)

Re: Another way to Replicate

From: "Chad Wagner" <chad(dot)wagner(at)gmail(dot)com>
To: "Alexander B(dot)" <burbello3000(at)yahoo(dot)com(dot)br>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Another way to Replicate
Date: 2007-01-19 18:49:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On 1/19/07, Alexander B. <burbello3000(at)yahoo(dot)com(dot)br> wrote:
> I would like to know if is possible to replicate in postgres applying
> binary logs (wal logs) like the same way is done on Oracle!!
> Did anybody tried to do that?

Oracle doesn't use binary logs for replication, for regular snapshots it
uses a "materialized log" -- which is nothing more than a table with a
primary key and what type of change.  If we are talking multi-master
replication, then Oracle uses Advanced Queues (essentially another table)
and pushes the data.  All off this occurs over DB links.

As for binary (archived redo) logs in Oracle, they can be used for a Hot
Standby.  Which PostgreSQL also supports, as I understand it this is a new
feature for 8.2.

I personally haven't investigated Slony, but I believe it functions similar.

Applying the simple ideia:
> - for each archived Wal logs, transfer to slave server;
> - after transfer, apply recover on postgres;
> - repeat the steps above, all the time;

Again, this is a hot (warm in PostgreSQL) standby database.  I don't think
you can bring online a database in read only while it is actively applying
the archived WAL logs.


In response to


pgsql-admin by date

Next:From: Chad WagnerDate: 2007-01-19 18:50:42
Subject: Re: Another way to Replicate
Previous:From: Alexander B.Date: 2007-01-19 18:41:58
Subject: Another way to Replicate

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group