| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Artem Gavrilov <artem(dot)gavrilov(at)percona(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Inaccurate statement about log shipping replication mode |
| Date: | 2025-09-03 05:59:50 |
| Message-ID: | aLfZVpV4eTtYCys6@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Sep 02, 2025 at 11:10:42AM -0400, Robert Treat wrote:
> So with that said, I would suggest fixing this by changing the first
> sentence of paragraph 4 to "It should be noted that file based log
> shipping is asynchronous", as this also emphasizes that this section
> is focused on file based wal shipping.
Not sure that there is a strong need for "file-based", still it is
true that we could just remove the inexact part of the sentence and
call it a day, as of:
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -527,8 +527,7 @@ protocol to make nodes agree on a serializable transactional order.
</para>
<para>
- It should be noted that log shipping is asynchronous, i.e., the WAL
- records are shipped after transaction commit. As a result, there is a
+ It should be noted that log shipping is asynchronous. As a result, there is a
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-09-03 07:37:08 | Re: Inaccurate statement about log shipping replication mode |
| Previous Message | PG Doc comments form | 2025-09-02 15:42:40 | pg_upgrade, can you use the rsync method of upgrading a standby if you used clone mode? |