From: | Дмитрий Сарафанников <dimon99901(at)mail(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Logical decoding on standby |
Date: | 2016-01-19 15:30:33 |
Message-ID: | 1453217433.421060638@f409.i.mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
If i try to create logical replication slot on standby i get error:
ERROR: logical decoding cannot be used while in recovery
In code i found this comment:
/* ----
* TODO: We got to change that someday soon...
*
* There's basically three things missing to allow this:
* 1) We need to be able to correctly and quickly identify the timeline a
* LSN belongs to
* 2) We need to force hot_standby_feedback to be enabled at all times so
* the primary cannot remove rows we need.
* 3) support dropping replication slots referring to a database, in
* dbase_redo. There can't be any active ones due to HS recovery
* conflicts, so that should be relatively easy.
* ----
*/
if (RecoveryInProgress())
ereport(ERROR,
(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
errmsg("logical decoding cannot be used while in recovery")));
When you plan to add logical decoding on standby?
it is useful to have separate standby server for logical replication that will not break the master if you make a mistake in plugin.
--
Regards
Dmitriy
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-01-19 15:37:02 | Re: Logical decoding on standby |
Previous Message | Dilip Kumar | 2016-01-19 15:00:17 | Re: Move PinBuffer and UnpinBuffer to atomics |