Re: pg_receivexlog add synchronous mode - Mailing list pgsql-hackers

From
Subject Re: pg_receivexlog add synchronous mode
Date
Msg-id A9C510524E235E44AE909CD4027AE196BF7C70D169@MBX-MSG-SV03.msg.nttdata.co.jp
Whole thread Raw
In response to Re: pg_receivexlog add synchronous mode  (<furuyao@pm.nttdata.co.jp>)
Responses Re: pg_receivexlog add synchronous mode  (<furuyao@pm.nttdata.co.jp>)
List pgsql-hackers
This patch was made by the following process.

1. post patch for additional pg_receivexlog synchronous mode.

2. In response to comment for the flush frequency, I revise the patch to do flush every consecutive message in
referenceto walreceiver.
 

3. The synchronization mode was necessary to reply after flush at a flush position, but --status-interval for setting
atleast 1 second, it was pointed out.
 
   Therefore I changed it to the patch to add the mode which the same interval flush with walreceiver, and I canceled
thesynchronization mode.
 

4. The refactor patch was offered, and there was the "--fsync-interval" option in the "pg_recvlogical" which specifies
aflush interval.
 
   I changed it to the patch which did flush specified interval by the "--fsync-interval" in the same way as
"pg_recvlogical".

5. Post the patch that reflects the comments centered on the document pointed out that.

6. The patch for correcting the operation at the time of specifying zero as "--status-interval" was offered.
   In response to it, those that modify the behavior of If you specify -1 or zero of the "fsync-interval" is this
patch.

Regards,

--
Furuya Osamu

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: refactoring allpaths.c (was Re: Suppressing unused subquery output columns)
Next
From: Krystian Piećko
Date:
Subject: sendLong in custom communication doesn't work