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.96) (envelope-from ) id 1vV3oF-00CnMv-3A for pgsql-admin@arkaria.postgresql.org; Mon, 15 Dec 2025 08:20:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vV3oD-00GWVJ-35 for pgsql-admin@arkaria.postgresql.org; Mon, 15 Dec 2025 08:19:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vV3oD-00GWUP-1l for pgsql-admin@lists.postgresql.org; Mon, 15 Dec 2025 08:19:58 +0000 Received: from mail-yx1-xb132.google.com ([2607:f8b0:4864:20::b132]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vV3oB-000pER-2K for pgsql-admin@postgresql.org; Mon, 15 Dec 2025 08:19:58 +0000 Received: by mail-yx1-xb132.google.com with SMTP id 956f58d0204a3-640d4f2f13dso3268543d50.1 for ; Mon, 15 Dec 2025 00:19:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765786794; x=1766391594; darn=postgresql.org; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:to :from:from:to:cc:subject:date:message-id:reply-to; bh=jZz5doKTYVSLXR9DhNpXwrh5Nzl8GsRCDS2OvwztXho=; b=Vbc48viFHt9jbKH+v4F03cY/G1v3rXwygtrevkjr7MTYEASbzW1UvPD01SEqlatkzO sUrLakqqiWA9ENabCAXPcvs72uNjFN1a1yQzgKiB9eiujxA5G25XSBkPmcSbrfb9/3cM C2fQ+z1QjaRd9F6WVel/xUqIvre/UZw0+/ZnBUzEdX0rgh6TdQXasOAmi/KIUZWe7u49 823pbD26GPkT93sUvm6rPa1fwBml9/Vf50EbAi7NefCDqyzyTSIh4/Nyqylb3meOvhl/ qrvseNQ8iawMzwRfu3teGvqtgvozUAGy9ysA7ay7jacZP6AX+AGv9Nt364sqxhulvCW6 FfnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765786794; x=1766391594; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:to :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=jZz5doKTYVSLXR9DhNpXwrh5Nzl8GsRCDS2OvwztXho=; b=VPLJXZndggJ1DMlPYJ8Nx4jYfEmbdiINxK8D4I2QqERqXZX6ehTPabTGWDiM6MN3TR O7/K7M0+jglh2jO7iJfMi8XyahGDWIlnM1NUmS8sYDDdPDIbh1hCnGODnRJV5JTNg4/A blNiOlaGozgi5+DuIa8S4JXpZYbFHROVL+gBw7RLH+5m9sClxrOXNzFDc7OLFQuWzmza KBTvbqhQk9oWrQVLP4/RtjodDr2e2NpPTBKfIF57QGRFaKilcP440JszAphBAvChPsfg Xvk6QABVscqkPG8gwaptlSN5XekRyMJRa8Y+ycmAtkBp7xNCWAlg76AiZvIOTRHlWJ8F w19g== X-Forwarded-Encrypted: i=1; AJvYcCVlPc6gwCaI6fLSod2egUoXXDbfJ052nx7O5ZTtQckVKzqP6kAKLFK67erNCxvCYhUShMaBREjOFbLNsg==@postgresql.org X-Gm-Message-State: AOJu0YwC+ssrRnaWRWG7v3zjNr9Aio5OkCIe5kV31gzv3G1CLDOfpyiq 4nP/tJrSmalyDR46OMd3liEWXWyJ9HH/YxXFPgiIIFdm/mV69lc1/Kg2X0+7Xg== X-Gm-Gg: AY/fxX5YLbvCUPu74KV+fHASmgEPaJCCcDQj67DcIOs/GnfBhiMIzgoV3OVa6b9dk9g UAqLFwWW9wiXLcEHbbuWqNJhBK3jCbLire4pyQLbzfk9jqeXUgHcWDaBsKos+Xo9Wu9fqUz5sw8 KJn6OdoIKdsnIbFmVOiWfkYbMADqEl//3rQS5s7oaPAdFvZwFxNQgmURjd1SB74YcmPkz04ayHP 5E3aA+R+tZFeaPgSvKKlK3mE8MWv4bLbOLSMjOfkdNitNQDAieQNGeHoyYyGmb4WtYof6wF2y53 OV8dWZfGPCW7SMcIXxlgDMIMJzuWHZRt4PaKrOe5hsz1fN3M0EKsSTNuADYARvlsXhRadps/Mr3 iuejLTZKHrch42MgyyibwLIQVmTvoU9JQAqz5oTHaD9tNJXlzU7q/wFYJdIVFrZ7F+zowoYtwuC KQhjcdsAdtDlj5QBayQmsxR716heqrgA9tRl9YGqkHSTeXEVXgV6PP8fFdazQs+3jmFasOgYJJj LzYFImCmg== X-Google-Smtp-Source: AGHT+IF52UWatEr2TXdUwF2M2ycd226TljfilvVbEqtb0UxRlvuhVvGjCaN4iugLou3VLNBIp1AiYA== X-Received: by 2002:a05:690e:1cb:b0:63f:7de1:7acf with SMTP id 956f58d0204a3-645555e8d74mr5880672d50.22.1765786793631; Mon, 15 Dec 2025 00:19:53 -0800 (PST) Received: from AM4P193MB2941.EURP193.PROD.OUTLOOK.COM ([2603:1026:c03:8c0e::5]) by smtp.gmail.com with ESMTPSA id 00721157ae682-78e74a43113sm25603337b3.51.2025.12.15.00.19.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Dec 2025 00:19:52 -0800 (PST) From: kasem adel To: Laurenz Albe , pgsql-admin Subject: Re: Wal file increase Thread-Topic: Wal file increase Thread-Index: AUF5anI2YaHEP911xq6wSXkemzP+eWxjMTNisoU2fLWAAA84AIAAAVAD X-MS-Exchange-MessageSentRepresentingType: 1 Date: Mon, 15 Dec 2025 08:19:40 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: ar-SA X-Mentions: laurenz.albe@cybertec.at X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 x-ms-reactions: allow Content-Type: multipart/alternative; boundary="_000_AM4P193MB29416485C01CC7DCC529C592AEADAAM4P193MB2941EURP_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_AM4P193MB29416485C01CC7DCC529C592AEADAAM4P193MB2941EURP_ Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable Dear @Laurenz Albe, -What exactly is a "replication interruption", and how do you diagnose it? We see replication slot restart every time in these period - Are you using streaming replication or logical replication? I have streaming replication for one node and another logical replication - If it is streaming replication, are you using a replication slot? Yes have replication slot - It is expected that if you suspend replication and have a replication slo= t, WAL will pile up on the primary. But what is the connection with pg_basebackup? Yes still exist. =C7=CD=D5=E1 =DA=E1=EC Outlook =E1=DC iOS ________________________________ =E3=E4: Laurenz Albe =FE=FE=CA=E3 =C7=E1=C5=D1=D3=C7=E1: Monday, December 15, 2025 10:09:00 AM =C5=E1=EC: kasem adel ; pgsql-admin =FE=FE=C7=E1=E3=E6=D6=E6=DA: Re: Wal file increase On Mon, 2025-12-15 at 07:25 +0000, kasem adel wrote: > Thanks for your support We have physical replication connection with Post= gres node standby > and have another replication slot with logical replication with another n= ode and every day > after run pg_basebackup we face huge number of file created and size per = every hour is 23GB > and in normal size is 0.8 GB and in logical replication we see in logs it= =92s in same > checkpoint but baseline change and we run pg_basebackup with -X fetch -C = fast. pg_basebackup does not increase the WAL volume, except by the full-page ima= ges that get written after any checkpoint. So you'd need to find an explanation for tha= t. "-X fetch" is not a good choice. Use "-X stream". Anyway, you didn't answer all my questions. Yours, Laurenz Albe --_000_AM4P193MB29416485C01CC7DCC529C592AEADAAM4P193MB2941EURP_ Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable

-What exactly is a "replica= tion interruption", and how do you diagnose it?
We see replication slot restart every time in these period 
- Are you using streaming replication or l= ogical replication?
I have streaming replication for one node and another logical replication&n= bsp;
- If it is streaming replication, are you = using a replication slot?
Yes have replication slot
- It is expected that if you suspend = replication and have a replication slot, WAL will
  pile up on the primary.  But w= hat is the connection with pg_basebackup?
Yes still exist.
=C7=CD=D5=E1 =DA=E1=EC Outlook =E1=DC iOS
=E3=E4: Laurenz Albe <la= urenz.albe@cybertec.at>
=FE=FE=CA=E3 =C7=E1=C5=D1=D3=C7=E1: Monday, December 15, 2025 10:09:= 00 AM
=C5=E1=EC: kasem adel <kasemadel8@gmail.com>; pgsql-admin <= pgsql-admin@postgresql.org>
=FE=FE=C7=E1=E3=E6=D6=E6=DA: Re: Wal file increase
 
On Mon, 2025-12-15 at 07:25 +0000, kasem adel wrot= e:
> Thanks for your support We have physical replication connection with P= ostgres node standby
> and have another replication slot with logical replication with anothe= r node and every day
> after run pg_basebackup we face huge number of file created and size p= er every hour is 23GB
> and in normal size is 0.8 GB and in logical replication we see in logs= it=92s in same
> checkpoint but baseline change and we run pg_basebackup with -X fetch = -C fast.

pg_basebackup does not increase the WAL volume, except by the full-page ima= ges that get
written after any checkpoint.  So you'd need to find an explanation fo= r that.

"-X fetch" is not a good choice.  Use "-X stream".=

Anyway, you didn't answer all my questions.

Yours,
Laurenz Albe
--_000_AM4P193MB29416485C01CC7DCC529C592AEADAAM4P193MB2941EURP_--