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

From Alvaro Herrera
Subject Re: [HACKERS] Improve logical decoding error message (was wal_level> WAL_LEVEL_LOGICAL)
Date
Msg-id 20170523005516.wl65wp2khrp7mr65@alvherre.pgsql
Whole thread Raw
In response to Re: [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
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.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Neha Khatri
Date:
Subject: Re: [HACKERS] Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Some thoughts about SCRAM implementation