Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders

Mark Dilger <hornschnorter(at)gmail(dot)com> writes:
>> On Apr 22, 2017, at 11:40 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In short then, I propose the attached patch to make these cases fail
>> more reliably. We might extend this later to allow the old behaviors
>> to be explicitly opted-into, but we don't seem to need that today.

> I pulled fresh sources with your latest commit, 7d68f2281a4b56834c8e5648fc7da0b73b674c45,
> and the tests consistently fail (5 out of 5 attempts) for me on my laptop with:

> Are the errors expected now?

Yes, as of right now, if HEAD *doesn't* fail the src/test/recovery tests
for you in an assert-enabled build, that would be surprising. The next
step is to actually fix the bugs ... but the point of commit 7d68f2281
was to make these failures reproducible, which they were not before.

regards, tom lane