Re: Another way to Replicate

Поиск
Список
Период
Сортировка
От Chad Wagner
Тема Re: Another way to Replicate
Дата
Msg-id 81961ff50701191049r5f729dcbqd074731edd0e6de1@mail.gmail.com
обсуждение исходный текст
Ответ на Another way to Replicate  ("Alexander B." <burbello3000@yahoo.com.br>)
Ответы Re: Another way to Replicate  ("Chad Wagner" <chad.wagner@gmail.com>)
Re: Another way to Replicate  ("Andy Shellam (Mailing Lists)" <andy.shellam-lists@mailnetwork.co.uk>)
Список pgsql-admin
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/

В списке pgsql-admin по дате отправления:

Предыдущее
От: "Alexander B."
Дата:
Сообщение: Another way to Replicate
Следующее
От: "Chad Wagner"
Дата:
Сообщение: Re: Another way to Replicate