From: | <furuyao(at)pm(dot)nttdata(dot)co(dot)jp> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Cc: | <teranishih(at)nttdata(dot)co(dot)jp> |
Subject: | pg_receivexlog add synchronous mode |
Date: | 2014-06-05 08:09:44 |
Message-ID: | A9C510524E235E44AE909CD4027AE196BAAA06D7DB@MBX-MSG-SV03.msg.nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
This patch implements a pg_receivexlog add synchronous mode.
Now, synchronous(synchronous_commit = remote_write) is supported.
But synchronous(synchronous_commit = remote_write), if the server crashes then WAL file may not to be flushed to disk , causing data loss.
Synchronous(synchronous_commit = on) mode offers the ability to confirm WAL have been streamed in the same way as synchronous replication.
If an output is used as a different disk from the directory where the transaction log should be stored.
Prevent the loss of data due to disk failure.
the additional parameter(-m) and replicationslot specify, that its synchronous mode.
All received WAL write after, flush is executed and reply flush position.
Flush is not performed every time write, it is performed collectively like walrecever.
Regards,
--
Furuya Osamu
Attachment | Content-Type | Size |
---|---|---|
pg_receivexlog-add-synchronous-mode.patch | application/octet-stream | 8.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-06-05 08:11:02 | Re: slotname vs slot_name |
Previous Message | Amit Langote | 2014-06-05 07:56:08 | Re: Need to backpatch 2985e16 to 9.3 and further (HS regression test out) |