From: | Dan shmidt <dshmidt(at)hotmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Logical replication from multiple masters - master starvation |
Date: | 2020-08-04 20:40:20 |
Message-ID: | MN2PR02MB644766952475759D0A3211F5A44A0@MN2PR02MB6447.namprd02.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi everyone,
I'm using postgres 11.4
I have a configuration in which there's one subscriber (slave) node which subscribes to several (4) publisher nodes (master).
I noticed one of the master servers keeps lagging behind. I noticed that the replication worker on the master keeps failing on timeouts.
When querying pg_stat_subscription on the slave I noticed that last_msg_send_time for this master hardly ever updates.
Could this be starvation?
Is there any special configuration on either side (master/slave) that can help reduce that?
What's the logic on the slave that chooses from which subscription to process incoming data?
How can I further debug this?
Thanks,
Dan.
Sent from Outlook<http://aka.ms/weboutlook>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-08-04 20:59:13 | Re: Postgres 12 - default value for text column |
Previous Message | Raj Gandhi | 2020-08-04 20:35:16 | Postgres 12 - default value for text column |