Performance improvement: implement reporting from read-only replica (from TrekGlobal)
Description
Environment
None
is duplicated by
relates to
Activity
Carlos Ruiz July 26, 2020 at 11:01 AM
Carlos Ruiz
July 26, 2020 at 11:01 AM
Thanks @Heng Sin Low, opened https://idempiere.atlassian.net/browse/IDEMPIERE-4385#icft=IDEMPIERE-4385 for that
Carlos Ruiz July 26, 2020 at 10:58 AM
Carlos Ruiz
July 26, 2020 at 10:58 AM
Heng Sin Low July 26, 2020 at 10:48 AM
Heng Sin Low
July 26, 2020 at 10:48 AM
Hi @Carlos Ruiz , the changes at DB.close breaks the try with resource contract with Statement/PrepareStatement. That’s a violation of a well known Java Coding Standard/Pattern (In fact, Eclipse will raise warning if you don’t use try-with-resources with statement/preparestatement).
Carlos Ruiz August 30, 2019 at 9:30 AM
Carlos Ruiz
August 30, 2019 at 9:30 AM
Carlos Ruiz May 2, 2019 at 11:59 AM
Carlos Ruiz
May 2, 2019 at 11:59 AM
Documentation:
Sometimes postgresql throws error when running a query on a read-only replica - this can happen because the query takes too long.
In such cases, the following parameters can help:
https://www.postgresql.org/docs/9.6/runtime-config-replication.html#GUC-MAX-STANDBY-ARCHIVE-DELAY
max_standby_archive_delay = -1
max_standby_streaming_delay = -1
Fixed
Details
Details
Created December 18, 2018 at 1:13 PM
Updated December 30, 2020 at 2:08 PM
Resolved December 18, 2018 at 1:24 PM
Bringing an improvement from TrekGlobal to implement reporting from read-only replica(s) on amazon/postgresql