Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 478159FB475 for ; Fri, 19 Jan 2007 14:50:13 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 34787-09 for ; Fri, 19 Jan 2007 14:49:57 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by postgresql.org (Postfix) with ESMTP id 041199FB472 for ; Fri, 19 Jan 2007 14:49:56 -0400 (AST) Received: by nf-out-0910.google.com with SMTP id x4so572365nfb for ; Fri, 19 Jan 2007 10:49:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=VLyLZhKIztEbdAilrjEdRDA3m6Yy0t6dt83iQz0ZvW/+F3ahne+oDUWpyjXuiKPRQ3261P82wvlX/d6OknGZxDQPcuZFKu1yicgnliEh8DBEw3k9pqHe+Br7EJU5J1kRvcQEbEIPjsS3ItiSMzxDHdfgO92rx02iDogiz0/DQ6o= Received: by 10.48.48.13 with SMTP id v13mr2601357nfv.1169232595105; Fri, 19 Jan 2007 10:49:55 -0800 (PST) Received: by 10.48.230.1 with HTTP; Fri, 19 Jan 2007 10:49:55 -0800 (PST) Message-ID: <81961ff50701191049r5f729dcbqd074731edd0e6de1@mail.gmail.com> Date: Fri, 19 Jan 2007 13:49:55 -0500 From: "Chad Wagner" To: "Alexander B." Subject: Re: Another way to Replicate Cc: "pgsql-admin@postgresql.org" In-Reply-To: <45B110F6.9080607@yahoo.com.br> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20967_4578695.1169232595008" References: <45B110F6.9080607@yahoo.com.br> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/173 X-Sequence-Number: 24329 ------=_Part_20967_4578695.1169232595008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/19/07, Alexander B. 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. -- Chad http://www.postgresqlforums.com/ ------=_Part_20967_4578695.1169232595008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 1/19/07, Alexander B. <burbello3000@yahoo.com.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.



--
Chad
http://www.postgresqlforums.com/ ------=_Part_20967_4578695.1169232595008--