Re: Re: pglogical_output - a general purpose logical decoding output plugin

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Tomasz Rybak <tomasz(dot)rybak(at)post(dot)pl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: pglogical_output - a general purpose logical decoding output plugin
Date: 2016-01-21 16:38:03
Message-ID: CA+TgmoYZnCnWkzBzVydCkb-y7KcEi289HKx5hfyumcGokL1OOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 20, 2016 at 12:54 AM, Craig Ringer <craig(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2016-01-21 17:33:06 Re: Batch update of indexes
Previous Message Robert Haas 2016-01-21 16:37:27 Re: Re: pglogical_output - a general purpose logical decoding output plugin