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

Поиск
Список
Период
Сортировка
От Neha Khatri
Тема Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Дата
Msg-id CAFO0U+-pc_fQARUUUwNZRBtqJtSTfgtL+5Cy_nct4NHOcEAXdg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Improve logical decoding error message (was wal_level> WAL_LEVEL_LOGICAL)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: [HACKERS] Improve logical decoding error message (was wal_level> WAL_LEVEL_LOGICAL)  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Дерево обсуждения

On Tue, 23 May 2017 at 10:55 am, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Neha Khatri wrote:
> On Tue, May 23, 2017 at 10:26 AM, Michael Paquier <michael.paquier@gmail.com

> > There is no wal_level higher than logical, so the current sense looks
> > perfectly fine to me.
>
> If there is no wal_level higher than logical, should the following error
> message indicate to set it >= logical.
>
>  select * from
> pg_create_logical_replication_slot('regression_slot','test_decoding');
>  ERROR:  logical decoding requires wal_level >= logical

I think it's purposefully ambiguous to cover a possible future
extension.

Should documentation also have similar statement and indicate future possibility.

What is the benefit of having it just in error message.

Regards,
Neha
--
Cheers,
Neha

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

Предыдущее
От: Mahi Gurram
Дата:
Сообщение: [HACKERS] Regarding Postgres Dynamic Shared Memory (DSA)
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [HACKERS] Tightening isspace() tests where behavior should matchSQL parser