Re: POC: enable logical decoding when wal_level = 'replica' without a server restart

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Дата
Msg-id CAA4eK1JNwVPPYBeG4waLzEM3mdsMLXq3_QvoqJ5gjt40M61Drw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: POC: enable logical decoding when wal_level = 'replica' without a server restart  (shveta malik <shveta.malik@gmail.com>)
Ответы Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Список pgsql-hackers
On Wed, Oct 22, 2025 at 2:40 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> On Fri, Oct 17, 2025 at 11:09 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
>
> I want to discuss the create-publication case, which currently gives
> this warning:
>
> postgres=# create publication pub1 for all tables;
> WARNING:  logical decoding should be allowed to publish logical changes
> HINT:  Before creating subscriptions, set "wal_level" >= "logical" or
> create a logical replication slot when "wal_level" = "replica".
> CREATE PUBLICATION
>
> But is this warning really necessary during publication creation?
>

On HEAD, the WARNING/HINT is as follows for the above case:
WARNING:  "wal_level" is insufficient to publish logical changes
HINT:  Set "wal_level" to "logical" before creating subscriptions.

Shouldn't we simply change the HINT to "Set "wal_level" to "logical"
or create a logical replication slot before creating subscriptions."?

--
With Regards,
Amit Kapila.



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