AW: AW: AW: AW: AW: Replication Testing- How to introduce a Lag - Mailing list pgsql-novice
| From | Subramanian,Ramachandran |
|---|---|
| Subject | AW: AW: AW: AW: AW: Replication Testing- How to introduce a Lag |
| Date | |
| Msg-id | aa307627991c41f280bb6da27ebc9b1d@alte-leipziger.de Whole thread Raw |
| In response to | Re: AW: AW: AW: AW: Replication Testing- How to introduce a Lag (Laurenz Albe <laurenz.albe@cybertec.at>) |
| Responses |
Re: Replication Testing- How to introduce a Lag
|
| List | pgsql-novice |
By force of habit I used a mainframe term. I am sorry . RBA = Relative Byte Address. Used as Log Sequence Number. I noticed that if I insert one row in a table at the source, the difference in LSNs is not 1 . ( with a delibrately introduceddelay on the apply side ), It is sometimes 96, sometimes 296 ( for the same table two inserts ) . psql -h $SOURCE_HOST -p $SOURCE_PORT -c "select pg_wal_lsn_diff(pg_current_wal_lsn(),replay_lsn) from pg_stat_replication" Is there a method to calculate the APPROXIMATE amount of data in ( Bytes ) that are yet to be transfered from Source to Standby? LG Ram [Subramanian,Ramachandran IT-md-db] On Mon, 2026-03-23 at 16:36 +0000, Subramanian,Ramachandran wrote: > I noticed that RBAs are not incremented one for one . i.e 1 row > inserted does not mean RBA=RBA+1 . 1 row updated does not mean > RBA=RBA+1 > > I have ALTER SYSTEM SET recovery_min_apply_delay=300000 ; ( on the > stand by side ) > > On the Source side > A simple create table results in a RBA difference of 108328 > > A simple insert of 1 row results in a RBA difference of 296 > sometimes 96 > > Is there a way to estimate roughly the amount of data that remains to > be transfered ? I don't know what an RBA is... If you are using recovery_min_apply_delay, don't measure the replication lag with regard to the replay_lsn, because replayis deliberately delayed. Instead, measure the difference to flush_lsn, the WAL position successfully transferred to the standby and persisted there. Yours, Laurenz Albe Freundliche Grüße i. A. Ramachandran Subramanian Zentralbereich Informationstechnologie Alte Leipziger Lebensversicherung a.G. Hallesche Krankenversicherung a.G. Alte Leipziger Lebensversicherung a.G., Alte Leipziger-Platz 1, 61440 Oberursel Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), FrankKettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek Sitz Oberursel (Taunus) · Rechtsform VVaG · Amtsgericht Bad Homburg v. d. H. HRB 1583 · USt.-IdNr. DE 114106814 Hallesche Krankenversicherung a.G., Löffelstraße 34-38, 70597 Stuttgart Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), FrankKettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek Sitz Stuttgart · Rechtsform VVaG · Amtsgericht Stuttgart HRB 2686 · USt.-IdNr. DE 147802285 Beiträge zu privaten Kranken- und Pflegekrankenversicherungen unterliegen nicht der Versicherungsteuer (§ 4 Nr. 5 VersStG)· Versicherungsleistungen sowie Umsätze aus Versicherungsvertreter-/Maklertätigkeiten sind umsatzsteuerfrei Die Pflichtangaben der ALH Gruppe gemäß § 35a GmbHG bzw. § 80 AktG finden Sie hier: https://www.alte-leipziger.de/impressum ______________________ ALH Gruppe Alte Leipziger-Platz 1, 61440 Oberursel Tel.: +49 (6171) 66-4882 Fax: +49 (6171) 66-800-4882 E-Mail: ramachandran.subramanian@alte-leipziger.de www.alte-leipziger.de www.hallesche.de
pgsql-novice by date: