Re: Transaction-controlled robustness for replication

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Hodges <robert(dot)hodges(at)continuent(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Jens-Wolfhard Schicke <drahflow(at)gmx(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transaction-controlled robustness for replication
Date: 2008-08-13 09:06:17
Message-ID: 48A2A409.9060201@bluegap.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Alvaro Herrera wrote:
> Actually I think the idea here is to take certain WAL records, translate
> them into "portable" constructs, ship them,

At which point it clearly shouldn't be called a WAL shipping method.
What would it have to do with the WAL at all, then? Why translate from
WAL records at all, better use the real tuples right away. (Almost
needless to say that here, but obviously Postgres-R does it that way).

So far, Simon really seems to mean WAL shipping: "it allows WAL to be
used as the replication transport", see [1].

Regards

Markus Wanner

[1]: mail to -hackers from Simon, Subject: "Plans for 8.4":
http://archives.postgresql.org/pgsql-hackers/2008-07/msg01010.php

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-08-13 09:12:42 Re: temporary statistics option at initdb time
Previous Message Markus Wanner 2008-08-13 07:35:56 Re: Transaction-controlled robustness for replication