Re: warning to publication created and wal_level is not set tological
| От | Andres Freund |
|---|---|
| Тема | Re: warning to publication created and wal_level is not set tological |
| Дата | |
| Msg-id | 20190325180613.57wjbefv2sxylogl@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: warning to publication created and wal_level is not set to logical (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: warning to publication created and wal_level is not set to logical
|
| Список | 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 по дате отправления: