Re: warning to publication created and wal_level is not set tological - Mailing list pgsql-hackers

From Andres Freund
Subject Re: warning to publication created and wal_level is not set tological
Date
Msg-id 20190325180613.57wjbefv2sxylogl@alap3.anarazel.de
Whole thread Raw
In response to Re: warning to publication created and wal_level is not set to logical  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: warning to publication created and wal_level is not set to logical
List pgsql-hackers
Hi,

On 2019-03-25 13:53:32 -0400, Tom Lane wrote:
> One idea that might be useful is to have walsenders refuse to transmit
> any logical-replication data if they see wal_level is too low.  That
> would get users' attention pretty quickly.

They do:


/*
 * Load previously initiated logical slot and prepare for sending data (via
 * WalSndLoop).
 */
static void
StartLogicalReplication(StartReplicationCmd *cmd)
{
    StringInfoData buf;

    /* make sure that our requirements are still fulfilled */
    CheckLogicalDecodingRequirements();

and CheckLogicalDecodingReqs contains:

    if (wal_level < WAL_LEVEL_LOGICAL)
        ereport(ERROR,
                (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
                 errmsg("logical decoding requires wal_level >= logical")));


Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Assert failure when validating foreign keys
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)