From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Marko Kreen <markokr(at)gmail(dot)com> |
Subject: | Re: Core team statement on replication in PostgreSQL |
Date: | 2008-05-29 21:52:37 |
Message-ID: | 7290.1212097957@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> I would have thought the read only piece would have been more important than
> the synchronous piece. In my experience readable slaves is the big selling
> point in both Oracle and MySQL's implementations, and people are not nearly
> as concerned if there is a small asynchronous window.
Actually, it's the "easy to use" piece that's near the front of my own
priority list. In any case, the expectation that we can get the log
shipping fixed sooner than we can get read-only slaves has nothing to do
with the relative desirability of the pieces; it's a technical judgment
based on what we can see of the problems' difficulty.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-05-29 21:54:36 | Re: Core team statement on replication in PostgreSQL |
Previous Message | Robert Treat | 2008-05-29 21:42:16 | Re: Core team statement on replication in PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-05-29 21:54:36 | Re: Core team statement on replication in PostgreSQL |
Previous Message | Mike | 2008-05-29 21:43:32 | Re: intercepting WAL writes |