Re: Fix logical decoding sendtime update

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix logical decoding sendtime update
Date: 2015-06-10 16:00:05
Message-ID: 20150610160005.GA21817@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2015-06-10 16:10:50 Re: replication slot restart_lsn initialization
Previous Message Andres Freund 2015-06-10 15:58:13 Re: s_lock() seems too aggressive for machines with many sockets