Re: Inaccurate statement about log shipping replication mode

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: 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-08-25 07:58:29
Message-ID: 568ff8638e011b2726d06a4b95124ec51ee1e5af.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, 2025-08-21 at 15:20 +0000, 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) states: "It should be noted that log shipping is
> asynchronous, i.e., the WAL records are shipped after transaction commit.".
> This statement is misleading because the same page includes a section about
> configuring synchronous streaming replication. To avoid confusion, I think
> it makes sense to specify that record-based log shipping can be configured
> as either asynchronous or synchronous.

I think that the statement you quote is not only misleading, but wrong.
WAL can get shipped before the transaction commits. Perhaps the sentence
had better be

It should be noted that by default, log shipping is asynchronous, i.e.,
the primary server does not wait until the standby receives the data.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Cheng Ding 2025-08-26 20:13:59 Ambiguity in VALUES synopsis: LIMIT vs FETCH
Previous Message Wim Bertels 2025-08-25 07:54:51 Re: Example on difference between CREATE MATERIALIZED VIEW and standard VIEW has typo