Re: libpq changes for synchronous replication

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq changes for synchronous replication
Date: 2010-11-19 16:58:12
Message-ID: 1290185828-sup-4858@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Tom Lane's message of vie nov 19 12:25:13 -0300 2010:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Thu, Nov 18, 2010 at 7:43 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> >> The patch is touching protocol.sgml as follows. Isn't this enough?
>
> > How about some updates to the "Message Flow" section, especially the
> > section on "COPY Operations"?
>
> Yeah. You're adding a new fundamental state to the protocol; it's not
> enough to bury that in the description of a message format. I don't
> think a whole lot of new verbiage is needed, but the COPY section needs
> to point out that this is a different state that allows both send and
> receive, and explain what the conditions are for getting into and out of
> that state.

Is it sane that the new message has so specific a name?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-19 17:04:28 Re: libpq changes for synchronous replication
Previous Message Tom Lane 2010-11-19 16:57:09 Re: Latches with weak memory ordering (Re: max_wal_senders must die)