Re: Inaccurate statement about log shipping replication mode

2025-09-04 Thread Michael Paquier
On Wed, Sep 03, 2025 at 09:37:08AM +0200, Laurenz Albe wrote: > I agree that it is a worthwhile goal to clarify the terms, and I > think that the whole chapter should be reorganized: > > Sections 26.2.5. to 26.2.9. should be moved to a new chapter > 26.3. "Streaming Replication" (which will renumb

Re: Inaccurate statement about log shipping replication mode

2025-09-03 Thread Laurenz Albe
On Tue, 2025-09-02 at 11:10 -0400, Robert Treat wrote: > I think the issue here is that this section is supposed to focus on > continuous archiving / file based WAL shipping, which is asynchronous. > All of the complexity that is being discussed in this thread is really > about WAL streaming, which

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Michael Paquier
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

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Artem Gavrilov
Oh, sorry I made a typo, it should be "is always async". I was referring to this statement in docs about cascading replication: "Cascading replication is currently asynchronous". It sounds to me like the whole replication setup is async (M -> U ->D), but it's only the (U -> D) part that is always a

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Robert Treat
On Tue, Sep 2, 2025 at 8:48 AM Laurenz Albe wrote: > > On Tue, 2025-09-02 at 11:22 +0200, Artem Gavrilov wrote: > > My original problem was with the first sentence "It should be noted > > that log shipping is asynchronous". I think your original suggestion > > "It should be noted that by default,

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Laurenz Albe
On Tue, 2025-09-02 at 11:22 +0200, Artem Gavrilov wrote: > My original problem was with the first sentence "It should be noted > that log shipping is asynchronous". I think your original suggestion > "It should be noted that by default, log shipping is asynchronous" > sounds good as it highlights f

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Laurenz Albe
On Mon, 2025-09-01 at 13:51 +0200, Artem Gavrilov wrote: > As I understand in configuration `Master > -> Upstream -> Downstream` replication between Master And Upstream > still can be synchronous, while between Upstream and Downstream is't > always async. Am I wrong here?

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Laurenz Albe
On Mon, 2025-09-01 at 13:51 +0200, Artem Gavrilov wrote: > As I understand in configuration `Master > -> Upstream -> Downstream` replication between Master And Upstream > still can be synchronous, while between Upstream and Downstream is't > always async. Am I wrong here? I don't quite understand.

Re: Inaccurate statement about log shipping replication mode

2025-09-02 Thread Laurenz Albe
On Mon, 2025-09-01 at 08:20 +0900, Michael Paquier wrote: > On Wed, Aug 27, 2025 at 02:13:21PM +0200, Laurenz Albe wrote: > > Here is a patch for that. > > --- a/doc/src/sgml/high-availability.sgml > > +++ b/doc/src/sgml/high-availability.sgml > > @@ -527,8 +527,8 @@ protocol to make nodes agree on

Re: Inaccurate statement about log shipping replication mode

2025-09-01 Thread Artem Gavrilov
On Mon, Sep 1, 2025 at 1:20 AM Michael Paquier wrote: > > Yep, the original statement is rather inexact. Now, your new wording > does not make me really comfortable with the case of cascading stanbys > in scope, because the asynchronous property applies to them all the > time. This is another u

Re: Inaccurate statement about log shipping replication mode

2025-08-31 Thread Michael Paquier
On Wed, Aug 27, 2025 at 02:13:21PM +0200, Laurenz Albe wrote: > Here is a patch for that. > --- a/doc/src/sgml/high-availability.sgml > +++ b/doc/src/sgml/high-availability.sgml > @@ -527,8 +527,8 @@ protocol to make nodes agree on a serializable > transactional order. > > > > - It sho

Re: Inaccurate statement about log shipping replication mode

2025-08-27 Thread Laurenz Albe
On Mon, 2025-08-25 at 09:58 +0200, Laurenz Albe wrote: > On Thu, 2025-08-21 at 15:20 +, PG Doc comments form wrote: > > Page: https://www.postgresql.org/docs/17/warm-standby.html > > > > The documentation page about Log-Shipping Standby Servers after describing > > that there are file-based lo

Re: Inaccurate statement about log shipping replication mode

2025-08-25 Thread Laurenz Albe
On Thu, 2025-08-21 at 15:20 +, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/17/warm-standby.html > > The documentation page about Log-Shipping Standby Servers after describing > that there are file-based log shipping and record-based log shipping > (streaming replication

Inaccurate statement about log shipping replication mode

2025-08-22 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/warm-standby.html Description: Hello, The documentation page about Log-Shipping Standby Servers after describing that there are file-based log shipping and record-based log shipping (stre