Re: warning to publication created and wal_level is not set to logical

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Lucas Viecelli <lviecelli199(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: warning to publication created and wal_level is not set to logical
Date: 2019-03-25 18:19:56
Message-ID: 21872.1553537996@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> 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:

Oh, OK, then this seems like it's basically covered already. I think
the original suggestion to add a WARNING during CREATE PUBLICATION
isn't unreasonable. But we don't need to do more than that (and it
shouldn't be higher than WARNING).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hadi Moshayedi 2019-03-25 18:57:48 Re: Fix foreign key constraint check for partitioned tables
Previous Message Fabien COELHO 2019-03-25 18:13:24 Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)