Re: Logical replication from PG v13 and below to PG v14 (devel version) is not working.

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Logical replication from PG v13 and below to PG v14 (devel version) is not working.
Дата
Msg-id CAA4eK1JAX8-HiKoZe-Z=KD107H1sTVRhtN31w_R_6R9LkEjcsw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Logical replication from PG v13 and below to PG v14 (devel version) is not working.  (Dilip Kumar <dilipbalaut@gmail.com>)
Ответы Re: Logical replication from PG v13 and below to PG v14 (devel version) is not working.
Re: Logical replication from PG v13 and below to PG v14 (devel version) is not working.
Список pgsql-hackers
On Tue, Sep 22, 2020 at 5:15 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Tue, Sep 22, 2020 at 12:02 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> >
> > I am not sure if this suggestion makes it better than what is purposed
> > by Dilip but I think we can declare them in define number order like
> > below:
> > #define LOGICALREP_PROTO_MIN_VERSION_NUM 1
> > #define LOGICALREP_PROTO_VERSION_NUM 1
> > #define LOGICALREP_PROTO_STREAM_VERSION_NUM 2
> > #define LOGICALREP_PROTO_MAX_VERSION_NUM LOGICALREP_PROTO_STREAM_VERSION_NUM
>
> Done this way.
>

- options.proto.logical.proto_version = LOGICALREP_PROTO_VERSION_NUM;
+ options.proto.logical.proto_version = MySubscription->stream ?
+ LOGICALREP_PROTO_STREAM_VERSION_NUM : LOGICALREP_PROTO_VERSION_NUM;

Here, I think instead of using MySubscription->stream, we should use
server/walrecv version number as we used at one place in tablesync.c.
Because say if we decide to add something additional for decode of
prepared xacts in PG14 then this check needs to be extended for stream
and prepared where as server version number check won't need to be
changed.

-- 
With Regards,
Amit Kapila.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Add information to rm_redo_error_callback()
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Parallel copy