pg_wal_replay_wait(): Fix typo in the doc
authorAlexander Korotkov <[email protected]>
Sun, 4 Aug 2024 17:26:48 +0000 (20:26 +0300)
committerAlexander Korotkov <[email protected]>
Sun, 4 Aug 2024 17:26:48 +0000 (20:26 +0300)
Reported-by: Kevin Hale Boyes
Discussion: https://postgr.es/m/CADAecHWKpaPuPGXAMOH%3DwmhTpydHWGPOk9KWX97UYhp5GdqCWw%40mail.gmail.com

doc/src/sgml/func.sgml

index 3cf896b22fad856794733c81c874a858d2182f27..0f7154b76ab7683e308c01f15a519f4757e1a013 100644 (file)
@@ -28990,7 +28990,7 @@ pg_current_wal_insert_lsn
 
    Then an application could run <function>pg_wal_replay_wait</function>
    with the <acronym>lsn</acronym> obtained from primary.  After that the
-   changes made of primary should be guaranteed to be visible on replica.
+   changes made on primary should be guaranteed to be visible on replica.
 
    <programlisting>
 postgres=# CALL pg_wal_replay_wait('0/306EE20');