Re: Issues with replication slots(which created manually) against logical replication

From: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
To: freebsdjlu <freebsdjlu(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issues with replication slots(which created manually) against logical replication
Date: 2020-04-13 08:12:22
Message-ID: CA+fd4k5P=-FtjLZGda6su1HekhWnpraTunAgbH0HcoBXqQTRdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 6 Apr 2020 at 23:32, freebsdjlu <freebsdjlu(at)gmail(dot)com> wrote:
>
> Hi
> I also met the same issue :
> WAL stream: ERROR: option "proto_version" = "1" is unknown
>
> do you know what is the root cause ?
>

It's usually a good idea to provide reproducible steps along with the
error you're having.

I suspect the error message came from contrib/test_decoding, and
'proto_version' option is used when starting logical replication. So
as far as I can imagine from the error message, I think that a server
attempted to start logical replication using a replication slot that
uses test_decoding rather than pgoutput. I suggest to check the decode
plug-in of the replication slot on the provider server that is used
for logical replication.

Regards,

--
Masahiko Sawada http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message wenjing 2020-04-13 08:25:02 [bug] Table not have typarray when created by single user mode
Previous Message Fabien COELHO 2020-04-13 07:54:01 Re: pgbench - test whether a variable exists