Some interesting work is starting to be done by users to test parallel
replication on real workloads. One issue that comes up is the performance on
workloads that have a relatively high number of lock conflicts between
transactions.
I made some patches (against latest 10.1) to help investigate and
Kristian Nielsen writes:
> 1. Adding status variables for parallel replication.
>
> http://lists.askmonty.org/pipermail/commits/2015-July/008131.html
>
> This patch adds new status variables that measure the time spent by parallel
> replication worker threads being
After initial tests of the n
2 matches
Mail list logo
