Re: making write location work (was: Efficient transaction-controlled synchronous replication) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: making write location work (was: Efficient transaction-controlled synchronous replication)
Date
Msg-id 29325.1300898681@sss.pgh.pa.us
Whole thread Raw
In response to making write location work (was: Efficient transaction-controlled synchronous replication)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: making write location work (was: Efficient transaction-controlled synchronous replication)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> Specifically, if we're not going to remove write location, then I
> think we need to apply something like the attached.

>              while (walrcv_receive(0, &type, &buf, &len))
>                  XLogWalRcvProcessMsg(type, buf, len);
> +            /* Let the master know that we received some data. */
> +            XLogWalRcvSendReply();

What if we didn't actually receive any new data?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: making write location work (was: Efficient transaction-controlled synchronous replication)
Next
From: Tom Lane
Date:
Subject: Re: Comments on SQL/Med objects