On 2015-06-10 17:57:42 +0200, Shulgin, Oleksandr wrote:
it turns out, that the code in WalSndWriteData is setting the timestamp of
the replication message just *after* it has been sent out to the client,
thus the sendtime field always reads as zero.
Ugh, what a stupid bug. Thanks!
Andres
--
Hi Hackers,
it turns out, that the code in WalSndWriteData is setting the timestamp of
the replication message just *after* it has been sent out to the client,
thus the sendtime field always reads as zero.
Attached is a trivial patch to fix this. The physical replication path
already does the
