Re: extensible options syntax for replication parser?

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: extensible options syntax for replication parser?
Дата
Msg-id CA+TgmoYmW4Comn4p4v5J_R3vtdCYNz-6KVO1_gmOL3Nc3tp4dA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: extensible options syntax for replication parser?  (tushar <tushar.ahuja@enterprisedb.com>)
Ответы Re: extensible options syntax for replication parser?  (tushar <tushar.ahuja@enterprisedb.com>)
Список pgsql-hackers
On Fri, Sep 24, 2021 at 2:28 PM tushar <tushar.ahuja@enterprisedb.com> wrote:
> Please refer this scenario where publication on v14RC1  and subscription
> on HEAD (w/patch)
>
> --create a subscription with parameter two_phase=1 on HEAD
>
> postgres=# CREATE SUBSCRIPTION r1015 CONNECTION 'dbname=postgres
> host=localhost port=5454' PUBLICATION p WITH (two_phase=1);
> NOTICE:  created replication slot "r1015" on publisher
> CREATE SUBSCRIPTION
> postgres=#
>
> --check on 14RC1
>
> postgres=# select two_phase from pg_replication_slots where
> slot_name='r105';
>   two_phase
> -----------
>   f
> (1 row)
>
> so are we silently ignoring this parameter as it is not supported on
> v14RC/HEAD ? and if yes then why not we just throw an message like
> ERROR:  unrecognized subscription parameter: "two_phase"

two_phase is new in v15, something you could also find out by checking
the documentation. Now if the patch changes the way two_phase
interacts with older versions, that's a bug in the patch and we should
fix it. But if the same issue exists without the patch then I'm not
sure why you are raising it here rather than on the thread where that
feature was developed.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: tushar
Дата:
Сообщение: Re: extensible options syntax for replication parser?
Следующее
От: Robert Haas
Дата:
Сообщение: Re: decoupling table and index vacuum