Re: loss of transactions in streaming replication

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-10-19T12:01:14Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Send status updates back from standby server to master, indicating how far
- b186523fd97c 9.1.0 cited
Allow bidirectional copy messages in streaming replication mode.
- d3d414696f39 9.1.0 cited

Attachments

walrcv_avoid_data_loss_v2.patch (text/x-diff) patch v2

On Wed, Oct 19, 2011 at 3:31 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> (2) for this marginal improvement, you're giving up including
>> PQerrorMessage(streamConn) in the error message that ultimately gets
>> omitted, which seems like a substantial regression as far as
>> debuggability is concerned.
>
> I think that it's possible to include PQerrorMessage() in the error
> message. Will change the patch.

Attached is the updated version of the patch. When walreceiver fails to
send data to WAL stream, it emits WARNING with the message including
PQerrorMessage(), and also it emits the following DETAIL message:

    Walreceiver process will be terminated after all available data
have been received from WAL stream.

Regards,

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