Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Date
Msg-id CAB7nPqQ9yO8qj1kLO=i6mLsQ4ZneuLyha6=NrzDkZR-dMPfTtA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)  (Neha Khatri <nehakhatri5@gmail.com>)
Responses Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)  (Neha Khatri <nehakhatri5@gmail.com>)
List pgsql-hackers
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.
-- 
Michael



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] translatable string fixes
Next
From: Alvaro Herrera
Date:
Subject: [HACKERS] pg_upgrade translation