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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Neha Khatri <nehakhatri5(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Date: 2017-05-23 00:26:04
Message-ID: CAB7nPqQ9yO8qj1kLO=i6mLsQ4ZneuLyha6=NrzDkZR-dMPfTtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 23, 2017 at 8:08 AM, Neha Khatri <nehakhatri5(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-05-23 00:28:27 pg_upgrade translation
Previous Message Alvaro Herrera 2017-05-23 00:15:57 Re: [HACKERS] translatable string fixes