Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uqS69-006ICC-7h for pgsql-docs@arkaria.postgresql.org; Mon, 25 Aug 2025 07:58:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uqS68-007AiS-CD for pgsql-docs@arkaria.postgresql.org; Mon, 25 Aug 2025 07:58:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uqS68-007AiI-3V for pgsql-docs@lists.postgresql.org; Mon, 25 Aug 2025 07:58:36 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uqS66-001co6-0E for pgsql-docs@lists.postgresql.org; Mon, 25 Aug 2025 07:58:35 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-afcb7ae31caso748877866b.3 for ; Mon, 25 Aug 2025 00:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1756108712; x=1756713512; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=zwPw0+xOxWX4VVGLGH82CxIJrPMOLAZo/pkXV5zRlKQ=; b=Dv1vDCFCzuryC6/yeuBXKOk05cFE0OMbSJg71atYFRzblnoOKpsAu5Vpr+mWt4FZj8 bHPcRGOq27dChuj9GN7kaoJT/RB0I8yn6Y4eH7eKy7vdHzhUrqn7BaQAOEtzFL0RSZFb UG3Ug1HZcw7NEbuqjnqrfWOmUd4j8iEFrutuEipeezigwu5i9y78DZvbvGvk+UbjnwaD zHbSzUefKUPg/l+b5N5hQ+elhw44Rj924zQY2hx8u0OTELvnAVM1eWdztdAGb2HrEkpO OP1wEnLkXMjPWHZs1NlPCKY0xZSYAVeEnFwAySpIMQsNW0eWokURw2Rksl6LCqFZwElz TcPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756108712; x=1756713512; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=zwPw0+xOxWX4VVGLGH82CxIJrPMOLAZo/pkXV5zRlKQ=; b=eK/oy14dRkp7oQA9DW7F05r6wjV+9DItMpWAQXe6hvWGg8BSXcvCNS7NxfooTegFfm R94/9DKlw15Epj6p/nI0VZrFKgD74uhL/KOeGSZPI0vlgfH6CrtPX+cVPYwAIM27S+p4 Ty8CllmInH+nvX68wrK/3GYoKrPdB5SXRFhwiXDNZ7frozIl3hgpexz7rGPjQikWjtXy pBC1h1LFM6CStmdyFUvz5dpUE8nsOQtjrBHZJ9wEqrnmhgApUzwgdmtRT3WPScB0nKCV FSyGxgbw+TPuNCQbWub0RMEI48lKWgeApihQylPZxwwYuR8x+ok1pm2OamzhbsLUq6sJ YmsQ== X-Forwarded-Encrypted: i=1; AJvYcCXul2zkb/TP//05xLXYHY1yeRndThmXsntsPPyQ8qrx0JB2ZxIdCLTcWwVxiS/zEv/cdu5t72cDrhSJ@lists.postgresql.org X-Gm-Message-State: AOJu0Ywmdjokszcj+roJ8r0g2pDM1M53+/8om3RJeuMh8uh4tXL7zYkc lvzkLJfRZ6Ksw+KhJMc5UdocolJ0wxH80HfYciln/2eiYXvumjfNs+I4MG1x7thI0j4= X-Gm-Gg: ASbGnct2N7d/U+pS9Pbmg4PsL9gW8XZnMQaI2UYwIW4U55HECmBXzbxi1M3XN/QK/UZ eP3CleUXzNWiZsWr3cWoycf7mWbPbfPJ9A5sCib8myflNH+yQGJEGJQrLlp4Z4+rD56g9JWK41m e4MtSPIdFUQjVsFUnyARPpdEoq5pAxLvFEHq/b/kiuLafDd6NaVPKwQmTqPdesmBViAXMq54OsO Ym4nqgM0WpKGG8OVbFR2h8jTSOIWEvRgNnYBzTepyCRjYI/SVVhtw9yiPh+9EAX90D4zcZs7Kkd K8aumKVYSiIVVYkAjAQPjIsnSj+XtCPDMsDSIHkqnIZnqKDgpQJnpFnfBhoTa+S47qzG+G1eoNg bC5Swe0nplB+guWdyXChUWgRinJf8f8w5kfCtQ6E31NqA4hx81T6VPt14995j X-Google-Smtp-Source: AGHT+IEQ8PGWeJ2vaXQY1ZWdshQeX4K6Xmarwct5SN2ey9p0nS/TmbfFce9PCloyA1GME4B6/d/9EQ== X-Received: by 2002:a17:907:7290:b0:afc:d209:37f2 with SMTP id a640c23a62f3a-afe297a25d4mr908906066b.61.1756108711776; Mon, 25 Aug 2025 00:58:31 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([2001:871:5e:8058:762e:f0c2:619d:667]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-afe66af4c06sm337386066b.38.2025.08.25.00.58.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Aug 2025 00:58:30 -0700 (PDT) Message-ID: <568ff8638e011b2726d06a4b95124ec51ee1e5af.camel@cybertec.at> Subject: Re: Inaccurate statement about log shipping replication mode From: Laurenz Albe To: artem.gavrilov@percona.com, pgsql-docs@lists.postgresql.org Date: Mon, 25 Aug 2025 09:58:29 +0200 In-Reply-To: <175578964049.806.14564779365418625473@wrigleys.postgresql.org> References: <175578964049.806.14564779365418625473@wrigleys.postgresql.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2025-08-21 at 15:20 +0000, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/17/warm-standby.html >=20 > The documentation page about Log-Shipping Standby Servers after describin= g > 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 abo= ut > configuring synchronous streaming replication. To avoid confusion, I thin= k > it makes sense to specify that record-based log shipping can be configure= d > 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