简体   繁体   English

WAL运送优先?

[英]WAL shipping priority?

In streaming replication, is there such a concept as WAL shipping priority (now or in future releases), where you could set the priority of how fast effects of a transaction should make it to standby servers? 在流复制中,是否存在WAL传送优先级(现在或将来的版本)这样的概念,您可以在其中设置事务应多快地影响到备用服务器的优先级?

Let's say i'm going to execute a non-critical update that would add 2GB of WAL files. 假设我要执行一个非关键更新,该更新将添加2GB的WAL文件。 It would be great if the shipping of that 2GB would not delay smaller and more important WAL files that I want to send to the standby servers immediately. 如果那2GB的出货量不会延迟我想立即发送到备用服务器的更小和更重要的WAL文件,那将是很好的。

Would this be possible now or in the future? 现在或将来有可能吗?

In the future, this looks like a possibility. 将来,这似乎是一种可能性。

Unknowingly you are asking for the Logical Decoding feature of PostgreSQL, that although nearly ready, may not be a solution for you today (Hint: It soon could be)... and to clarify, this is completely different from the very mature internal replication that has been available since 9.0. 不知不觉中,您正在要求PostgreSQL的Logical Decoding功能,尽管它几乎已经准备就绪,但今天可能不是您的解决方案(提示:很快就会出现)...并且需要澄清的是,这与非常成熟的内部复制完全不同从9.0开始提供。

You can read more about it here , but in essence, using this feature, you can define which tables to replicate, which not to. 您可以在此处阅读有关它的更多信息,但实质上,使用此功能,您可以定义要复制的表,而不要复制的表。 In fact you could have custom SELECT SQLs that tell the replication engine which data-set to replicate to the slaves... and if the said solution (down the line) matures enough, you could also probably prioritize data changes that get replicated off to the slaves, but I agree that its still not here yet. 实际上,您可能具有自定义的SELECT SQL,这些SQL告诉复制引擎要将哪些数据集复制到从属服务器上……并且,如果上述解决方案(在生产线中)足够成熟,则还可以优先考虑将数据更改复制到从属服务器上。奴隶,但我同意它还没有在这里。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM