From: | Lucas <root(at)sud0(dot)nz> |
---|---|
To: | |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 9.2 high replication lag |
Date: | 2021-07-25 08:33:59 |
Message-ID: | 9IUyTDCTXb7OhMjGR1ng9s6dxMnIilFs9w0rdKEQWOhWB0SWt-GqiJML-YNZadtZrnppAp0B5aCpY3HZcWvWSMrGEFOLIncUtj2BYm8qOUs=@sud0.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Version 9.2 is very old and has a lot of issues related to streaming replication. Additionally, it is already EOL.
Agreed.
> Furthermore, max_standby_streaming_delay has no relation with the streaming lag. It's associated with queries conflicting with data. This parameter will not speed up the WAL apply operation.
Yes, I know. But this parameter determines how long the standby server should wait before canceling standby queries that conflict with about-to-be-applied WAL entries. So, there could be lots of queries conflicting with about-to-be-applied WAL entries.
Again, I was not sure about what is causing the delay so I needed to try any possibility.
> Kindly consider upgrading to a supported version.
Yes. We have a project in progress to upgrade.
On top of that, I can say that I have restarted the slave and the replication is now normal.
[image.png]
You can see above that the replication delay is not passing 3 minutes, which is the max_standby_streaming_delay, but the actual average is 5 seconds. So, looks like rebooting the EC2 instance resolved the issue, but I do not know why.
Attachment | Content-Type | Size |
---|---|---|
publickey - root@sud0.nz - 0xC5E964A1.asc | application/pgp-keys | 3.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Avi Weinberg | 2021-07-25 14:01:38 | View of Union Multiple Tables - Only If table EXISTS |
Previous Message | Indrajit Datar | 2021-07-25 03:10:16 | regarding sql password auth |