[HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)

Поиск
Список
Период
Сортировка
От Neha Khatri
Тема [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Дата
Msg-id CAFO0U+_y8AyAcQLiF3S1i6yCNuYrcLNEd-BbzCuHiGOSejW=2A@mail.gmail.com
обсуждение исходный текст
Ответы Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
On Mon, May 22, 2017 at 11:08 PM, Neha Khatri <nehakhatri5@gmail.com> wrote:
As per my understabding, current postgres server supports only three
values for wal_level i.e. 'minimal' , 'replica' or 'logical'. But
following error message brought to notice that there are various code
spots that try to look for wal_level >= WAL_LEVEL_LOGICAL:

  select * from pg_create_logical_replication_slot('regression_slot',
'test_decoding');
  ERROR:  logical decoding requires wal_level >= logical

The Logical Decoding example in the documentation says:

  "Before you can use logical decoding, you must set wal_level to logical and max_replication_slots to at least 1."

But above error message is not exactly consistent with this documentation. Would it make sense to keep the error message and the documentation consistent like the attached.

Regards,
Neha
Вложения

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] PG10 Crash-safe and replicable Hash Indexes and UNIQUE
Следующее
От: Mark Rofail
Дата:
Сообщение: [HACKERS] GSoC 2017: Foreign Key Arrays