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+-bPe_fW8Zv0scTf-Y-k+con6MR-+3tDnVyXmGqf4G1ow@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL) (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: [HACKERS] Improve logical decoding error message (was wal_level> WAL_LEVEL_LOGICAL)
|
| Список | pgsql-hackers |
On Tue, May 23, 2017 at 10:26 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Tue, May 23, 2017 at 8:08 AM, Neha Khatri <nehakhatri5@gmail.com> wrote:
> 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.
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
Regards,
Neha
В списке pgsql-hackers по дате отправления: