Hi all,
I use logical replication to synchronize one big table + some small tables.
I know that if all tables are part of the same subscription it will be executed in transactional order. In other words, as long as the transaction that updated the big table is not
synchronized and executed on the subscriber side, no other transactions to the smaller tables will be synchronized to the subscriber side. Therefore, I split it into two subscriptions, one for the big table and another for the smaller tables.
-
How can I give higher priority to the subscription that synchronizing the smaller tables over the subscription that synchronizes the large table?
-
If that is not possible, how do I make sure the subscription that synchronizes the big table does not "starve" the subscription that synchronizes the small tables and leave it with almost no bandwidth?
Thanks!
IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you
should not copy or use this e-mail for any purpose nor disclose its contents to any person.
