Re: Hot standby and synchronous replication status

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot standby and synchronous replication status
Date: 2009-08-11 15:30:01
Message-ID: 3f0b79eb0908110830o3453b724v97bb6343409cda9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Tue, Aug 11, 2009 at 1:25 PM, Robert Haas<robertmhaas(at)gmail(dot)com> wrote:
> But just to kick off the discussion, here is Heikki's review of Synch
> Rep on 7/15:
>
> http://archives.postgresql.org/pgsql-hackers/2009-07/msg00913.php
>
> I think the key phrases in this review are "I believe we have
> consensus on four major changes" and "As a hint, I think you'll find
> it a lot easier if you implement only asynchronous replication at
> first. That reduces the amount of inter-process communication a lot."
> I think this points to a need to try to reduce the scope of this patch
> to something more manageable.  Heikki also points out that major
> change #4 was raised back in Decemeber, and I actually think #1 and #3
> were as well.

Thanks for clarifying the status. According to Heikki's advice,
I'm working at asynchronous replication at first. I'll submit the
patch by the next CommitFest at least.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-11 15:56:18 pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)
Previous Message Matt Culbreth 2009-08-11 15:26:18 Any tutorial or FAQ on building an extension?