From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, fazool mein <fazoolmein(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Synchronous replication - patch status inquiry |
Date: | 2010-09-01 00:45:47 |
Message-ID: | 20100901004547.GA6234@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 31, 2010 at 08:34:31PM -0400, Robert Haas wrote:
> On Tue, Aug 31, 2010 at 6:24 PM, David Fetter <david(at)fetter(dot)org> wrote:
> > On Tue, Aug 31, 2010 at 05:44:15PM -0400, Bruce Momjian wrote:
> >> fazool mein wrote:
> >> > Hello everyone,
> >> >
> >> > I'm interested in benchmarking synchronous replication, to see
> >> > how performance degrades compared to asynchronous streaming
> >> > replication.
> >> >
> >> > I browsed through the archive of emails, but things still seem
> >> > unclear. Do we have a final agreed upon patch that I can use?
> >> > Any links for that?
> >>
> >> No.
> >
> > That was a mite brusque and not super informative.
> >
> > There are patches, and the latest from Fujii Masao is probably
> > worth looking at :)
>
> I am pretty sure, however, that the performance will be terrible at
> this point. Heikki is working on fixing that, but it ain't done
> yet.
Is this something for an eDB feature, or for community PostgreSQL,
or...?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2010-09-01 00:53:44 | Re: string function - "format" function proposal |
Previous Message | Robert Haas | 2010-09-01 00:35:47 | Re: Synchronous replication - patch status inquiry |