Re: Outdated replication protocol error?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com>, Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
Subject: Re: Outdated replication protocol error?
Date: 2021-06-16 23:17:27
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2021-06-16 15:59:11 -0700, Jeff Davis wrote:
> [ digging up old thread ]
> It seems everyone agrees that the current behavior is strange.

Yea. I don't remember the details, but I've also hit this problem since
in some odd circumstance while reviewing the "logical decoding on
standbys" patchset.

> Any ideas on a solution here?

I think we should explicitly compute the current timeline before using
ThisTimelineID. E.g. in StartReplication() call a new version of
GetFlushRecPtr() that also returns the current timeline id.


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2021-06-16 23:31:55 Re: PoC: Using Count-Min Sketch for join cardinality estimation
Previous Message Andres Freund 2021-06-16 23:00:22 Re: Split xlog.c