Previously, when pg_recvlogical lost connection, reconnected, and restarted
replication, data that had already been flushed could be streamed again.
This happened because the replication start position used when restarting
replication was taken from the last standby status message, which could be
older than the position of the last flushed data. As a result, some flushed
data newer than the replication start position could exist and be re-sent.
This commit fixes the issue by ensuring all written data is flushed to disk
before restarting replication, and by using the last flushed position as
the replication start point. This prevents already flushed data from being
re-sent.
Additionally, previously when the --no-loop option was used, pg_recvlogical
could exit without flushing written data, potentially losing data. To fix
this issue, this commit also ensures all data is flushed to disk before
exiting due to --no-loop.
Author: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Mircea Cadariu <cadariu.mircea@gmail.com>
Reviewed-by: Yilin Zhang <jiezhilove@126.com>
Reviewed-by: Dewei Dai <daidewei1970@163.com>
Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Discussion: https://postgr.es/m/CAHGQGwFeTymZQ7RLvMU6WuDGar8bUQCazg=VOfA-9GeBkg-FzA@mail.gmail.com
output_fsync_lsn = output_written_lsn;
+ /*
+ * Save the last flushed position as the replication start point. On
+ * reconnect, replication resumes from there to avoid re-sending flushed
+ * data.
+ */
+ startpos = output_fsync_lsn;
+
if (fsync_interval <= 0)
return true;
PQExpBuffer query;
XLogRecPtr cur_record_lsn;
- output_written_lsn = InvalidXLogRecPtr;
- output_fsync_lsn = InvalidXLogRecPtr;
cur_record_lsn = InvalidXLogRecPtr;
/*
*/
exit(0);
}
- else if (noloop)
+
+ /*
+ * Ensure all written data is flushed to disk before exiting or
+ * starting a new replication.
+ */
+ if (outfd != -1)
+ OutputFsync(feGetCurrentTimestamp());
+
+ if (noloop)
+ {
pg_fatal("disconnected");
+ }
else
{
/* translator: check source for value for %d */