From: | Lucas Viecelli <lviecelli199(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | warning to publication created and wal_level is not set to logical |
Date: | 2019-03-21 22:45:59 |
Message-ID: | CAPjy-57rn5Y9g4e5u--eSOP-7P4QrE9uOZmT2ZcUebF8qxsYhg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi everyone,
A very common question among new users is how wal_level works and it
levels. I heard about some situations like that, a user create a new
publication in its master database and he/she simply does not change
wal_level to logical, sometimes, this person lost maintenance window, or a
chance to restart postgres service, usually a production database, and it
will discover that wal_level is not right just in subscription creation.
Attempting to iterate between new (and even experienced) users with logical
replication, 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:
-> WARNING: `PUBLICATION` created but wal_level `is` not set to logical,
you need to change it before creating any SUBSCRIPTION
Initiatives like this can make a good user experience with PostgreSQL and
its own logical replication.
Thanks
--
*Lucas Viecelli*
Attachment | Content-Type | Size |
---|---|---|
warning-publication-created-but-wal_level-not-set-to-logical.patch | text/x-patch | 5.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Nikita Glukhov | 2019-03-22 00:15:07 | Re: jsonpath |
Previous Message | Alvaro Herrera | 2019-03-21 22:18:24 | Re: partitioned tables referenced by FKs |