Re: Constant WAL replay
- From: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>
- To: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
- Cc: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org, eg(at)cybertec(dot)at
- Subject: Re: Constant WAL replay
- Date: Mon, 25 Apr 2005 21:25:13 +0200
- Message-id: <426D4419(dot)5050306(at)cybertec(dot)at>
Joshua D. Drake wrote:
Alvaro Herrera wrote:
On Sun, Apr 24, 2005 at 08:10:34AM +0200, Hans-Jürgen Schönig wrote:
The idea: We are looking for a way to implement a synchronous
single-master / multiple slaves systems.
Meanwhile we are able to serialize / deserialize WAL records and send
them to a group communication system which transports those records
to the slave database.
This is not hard to do.
In fact, I believe Command Prompt's Mammoth Replicator does exactly
this.
Very close. We don't use the WAL (yet, slated for probably 8.1) but we
do use a transaction log shipping method. So the implementation is
almost the same.
Sincerely,
Joshua D. Drake
Command Prompt, Inc.
Joshua,
This sounds interesting. If you don't use the WAL but a transaction log
shipping - what does it mean in terms of PostgreSQL? Do you create your
own transaction log?
What really interests me here: Where is you code located in order to
make sure that this things can work reliably?
Best regards,
Hans
--
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/664/393 39 74
www.cybertec.at, www.postgresql.at
Home |
Main Index |
Thread Index