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

From Tom Lane
Subject Re: warning to publication created and wal_level is not set to logical
Date
Msg-id 28237.1553450819@sss.pgh.pa.us
Whole thread Raw
In response to Re: warning to publication created and wal_level is not set tological  (David Fetter <david@fetter.org>)
Responses Re: warning to publication created and wal_level is not set to logical
Re: warning to publication created and wal_level is not set tological
List pgsql-hackers
David Fetter <david@fetter.org> writes:
> On Thu, Mar 21, 2019 at 07:45:59PM -0300, Lucas Viecelli wrote:
>> I am sending a patch that when an PUBLICATION is created and the
>> wal_level is different from logical prints a WARNING in console/log:

> Is a WARNING sufficient?  Maybe I'm misunderstanding something
> important, but I think the attempt should fail with a HINT to set the
> wal_level ahead of time.

That would be a booby-trap for dump/restore and pg_upgrade, so I don't
think making CREATE PUBLICATION fail outright would be wise.

> Possibly in a separate patch, setting the wal_level to anything lower
> than logical when publications exist should also fail.

I do not believe this is practical either.  GUC manipulation cannot
look at the catalogs.

I agree that it'd be nice to be noisier about the problem, but I'm
not sure we can do more than bleat in the postmaster log from time
to time if a publication is active and wal_level is too low.
(And we'd better be careful about the log-spam aspect of that...)

            regards, tom lane


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: CPU costs of random_zipfian in pgbench
Next
From: Alexander Korotkov
Date:
Subject: Re: jsonpath