Re: write ahead logging in standby (streaming replication)

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: write ahead logging in standby (streaming replication)
Date: 2009-11-13 09:18:15
Message-ID: 3f0b79eb0911130118x230a76cbo301fcfa1c0bd0f0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 13, 2009 at 3:17 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Yeah, that's the "other parts of the industry" I was referring to.  MySQL
> uses "semi-synchronous" to distinguish between its completely asynchronous
> default replication mode and one where it provides a somewhat safer
> implementation.  The description reads more as "asynchronous with some
> synchronous elements", not "one style of synchronous implementation".  None
> of their documentation wanders into the problem area here by calling it a
> true synchronous solution when it's really not--MySQL Cluster is their
> synchronous vehicle.
> It's fine to adopt the term "semi-synchronous", as it's become quite popular
> and people are going to label the PG implementation with it regardless of
> what is settled on here.  But we should all try to be careful to use it as
> correctly as possible.

OK. Let's think over what "recv ACK" and "fsync ACK"
synchronization modes should be called later.

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 Heikki Linnakangas 2009-11-13 09:23:43 Re: Check constraint on domain over an array not executed for array literals
Previous Message Hans-Jürgen Schönig 2009-11-13 08:52:37 Re: CommitFest 2009-09, two weeks on