备用节点上的逻辑解码 [英] Logical decoding on a standby node
问题描述
PostgreSQL 9.4引入了逻辑解码:
http:// www。 postgresql.org/docs/9.4/static/logicaldecoding.html
PostgreSQL 9.4 introduced Logical Decoding: http://www.postgresql.org/docs/9.4/static/logicaldecoding.html
它还具有级联流复制:
http://www.postgresql.org/docs/9.4/static/warm-standby。 html#CASCADING-REPLICATION
It also has Cascade Streaming Replication: http://www.postgresql.org/docs/9.4/static/warm-standby.html#CASCADING-REPLICATION
逻辑解码似乎基于流复制。但是,PostgreSQL服务器将拒绝在热备用数据库上启动逻辑复制插槽。
Logical Decoding seems to be based on Streaming Replication. However a PostgreSQL server will refuse to start a Logical replication slot on a hot standby. It will only allow Logical Decoding on the master node.
什么阻止热备用节点使用逻辑解码以级联方式复制自身?
What prevents a hot standby node to replicate itself in cascade using Logical Decoding?
推荐答案
工作 PostgreSQL 11的继续。
像pgologic这样的客户端将需要修改一旦基本功能在postgres中,就支持从备用服务器流式传输。
Clients like pglogical will need modification to support streaming from a standby once the basic functionality is in postgres.
这篇关于备用节点上的逻辑解码的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!