From: | Robert Hodges <robert(dot)hodges(at)continuent(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Markus Wanner <markus(at)bluegap(dot)ch>, 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-12 20:36:56 |
Message-ID: | C4C74278.DB67%robert.hodges@continuent.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Tom,
Could you expand on why logical application of WAL records is impractical in
these cases? This is what Oracle does. Moreover once you are into SQL a
lot of other use cases immediately become practical, such as large scale
master/slave set-ups for read scaling.
Thanks, Robert
On 8/12/08 12:40 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
>> On Tue, 2008-08-12 at 11:52 -0400, Bruce Momjian wrote:
>>> What is the attraction of logical application of the WAL logs?
>>> Transmitting to a server with different architecture?
>
>> Yes,
>
>> * different release
>> * different encoding
>> * different CPU architecture
>> * (with the correct transform) a different DBMS
>
> The notion that the WAL logs will ever be portable across such
> differences is so ... so ... well, it's barely worth laughing at.
>
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Robert Hodges, CTO, Continuent, Inc.
Email: robert(dot)hodges(at)continuent(dot)com
Mobile: +1-510-501-3728 Skype: hodgesrm
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-08-12 20:54:43 | Re: SeqScan costs |
Previous Message | Steve Atkins | 2008-08-12 20:25:57 | Re: Plugin system like Firefox |