Re: Re: pglogical_output - a general purpose logical decoding output plugin - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: pglogical_output - a general purpose logical decoding output plugin
Date
Msg-id CA+TgmoYZnCnWkzBzVydCkb-y7KcEi289HKx5hfyumcGokL1OOg@mail.gmail.com
Whole thread Raw
In response to Re: Re: pglogical_output - a general purpose logical decoding output plugin  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jan 20, 2016 at 12:54 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> The idea here is that we want downwards compatibility as far as possible and
> maintainable but we can't really be upwards compatible for breaking protocol
> revisions. So the output plugin's native protocol version is inherently the
> max protocol version and we don't need a separate MAX.

That idea seems right to me.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: pglogical_output - a general purpose logical decoding output plugin
Next
From: Konstantin Knizhnik
Date:
Subject: Re: Batch update of indexes