Hi, I propose the patch which reduces the amount of data loss on the standby.
If you create the trigger file after replication is terminated, the standby tries to replay all the WAL available in pg_xlog and the archive. This behavior is OK, and it's helpful to reduce the amount of data loss. But, if you create the trigger file while walreceiver is in progress, the standby replays only the WAL streamed from the master. Even if there are many outstanding WAL files in the archive or pg_xlog, they are not replayed. This might cause much data loss, so I think we should fix it. The attached patch changes the startup process so that it tries to replay all the WAL available in the archive and pg_xlog even if the trigger file is found while walreceiver is running. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
reduce_data_loss_v1.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
