Horton

Re: Outdated replication protocol error?

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-hackers@postgresql.org, Simon Riggs <simon@2ndquadrant.com>, Craig Ringer <craig.ringer@enterprisedb.com>
Date: 2021-06-16T23:17:27Z
Lists: pgsql-hackers 
Hi,

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.

Greetings,

Andres Freund

Commits

  1. Eliminate replication protocol error related to IDENTIFY_SYSTEM.

  2. Ensure ThisTimeLineID is valid before START_REPLICATION