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 1v5zjB-00FBHz-66 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2025 04:55:09 +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 1v5zj9-00DP6q-23 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2025 04:55:07 +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.94.2) (envelope-from ) id 1v5zj8-00DP6K-MY for pgsql-admin@lists.postgresql.org; Tue, 07 Oct 2025 04:55:07 +0000 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v5zj7-000nTb-1k for pgsql-admin@lists.postgresql.org; Tue, 07 Oct 2025 04:55:07 +0000 Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-33c9f2bcdceso37211321fa.2 for ; Mon, 06 Oct 2025 21:55:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759812904; x=1760417704; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ySURri+4LS6Hu+6C4GH8lZPxgkK5wCrgDwnWMN62Duw=; b=FsHteLd1eYC0girKPGaI3t3rDycBsvH5WkMkJKzhnUa3/e8gn8J4fHmT9Qwjg90R5j nnl7pMh0DY4hmTqy1z/5mPY4DMb0yR4jtAb2aYTklButQYIHNQFApUITGiU8NZyYcFqM 7uWAdNLGYM9T/KtDiGSRe/8/mF+bx9KqH2V7Djvpk4OL81RU3HJAIBpCyg99836V59cY Pu66PyeUf0+4KzHqRmQWQmIP/wvR0f/dieOq8kM4ymnTfYRhwRQF//q2XE5EDb9O9M9o EBYiuP/aLQxPFzmkWX54ZMNT2UFI9CUkIYyMH6kE2v3VmESWP+bZ0Gnh5D/MMqeLlWMb JSoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759812904; x=1760417704; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ySURri+4LS6Hu+6C4GH8lZPxgkK5wCrgDwnWMN62Duw=; b=k3gxpx5EYBVjyXhk+ljwKdpBFfISiGDCNK7yP8ZI8FAiKDNQ/HUpSmv/kLWSlm9CON GXof4Lvm1VPZur8gacNS4QxTu7N3CNaQAOl0L0XA4jb7tiK6Bbg2WcnNnpM4lLLWNCZw wewcf59Gr/23XO/UH8wxqVpuqfNN1u/hl9td+9St9oeoYjKu+q7go2ydT2pxbuRFGG+x oLvfEbJY6fCGhLLqAxasD6wazQmNzQIrsPwEmCEIoq/xeKzA3f5KWq2i+wJAzY4MN1MC 3mfiVV/akYQ4ubRHILrtj3bO+Ogfl3fhlbl0ZcoRVxzFN7hXVeSlKKLPf2JK5b60rv1t M08Q== X-Gm-Message-State: AOJu0YyZaz1D7sj+RXtFZvRufKjqciICquymVk9JNlKoRPwssRUh2+kc UmmtcKRSUHHGmtoe5/oqyU49aRn6ZrcLhOdOiC7T8WZK6u44KGiK6ZY+l9TO8kPuPs02a2dewQy 8XjJwb0nHoIVWx9cA8uEzxE/QrvIbVEdAaQ== X-Gm-Gg: ASbGnctd3wLzaQ2qJCxJIASIVNnDZveEb/OBkdVEHvLqGPv9dbXi83PaDi9HujO5vIX 23XBW/SgFl59yGgTAw6d8Nmiykcx3lyvA6lV+kyG2hsPR+4LqARhVvyM5irF0l+ThI8ffXHt4zE KQT6MLwuWato64F3aBSoOAZlNRN0wATYTS3U9/LqTxG0iRA/9NOvTs3bo+eIN7j74MP8lMD2Kws uME21QYxdtLJxxJNaPF0QcbOan5Qg0h X-Google-Smtp-Source: AGHT+IEeIbDm4gfvzo1VZ/Sp6ByB0NkjJHFnBo/Q8GK3cntvWwcnGX17LUG9M4p6pR85+gtyTZa0A71WVfGGpg/Z4oo= X-Received: by 2002:a05:651c:b06:b0:351:10a7:c6ca with SMTP id 38308e7fff4ca-374c36b981cmr44833971fa.7.1759812904286; Mon, 06 Oct 2025 21:55:04 -0700 (PDT) MIME-Version: 1.0 References: <469228369.58843.1759786683881@mail.yahoo.com> In-Reply-To: From: Raj Date: Tue, 7 Oct 2025 10:24:51 +0530 X-Gm-Features: AS18NWAvuL4Mv3HvMMm4sP-xyCIkGAcxpqb_xYLyoRrBwULBlTLZT-wPt4fyDXk Message-ID: Subject: Re: Wal_keep_size To: Thomas Carroll Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000007fdaa06408a5f2d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000007fdaa06408a5f2d Content-Type: text/plain; charset="UTF-8" Note archive mode is enabled. On Tue, 7 Oct 2025, 10:22 Raj, wrote: > If wal_keep_size is more than max_wal_size wouldn't it always trigger > checkpoint ? > > On Tue, 7 Oct 2025, 03:08 Thomas Carroll, wrote: > >> Hope nobody minds me chipping in here. >> >> The answer is "not necessarily." The names make them seem closely >> related, but not so much. >> >> max_wal_size is all about *checkpoints*. When the WAL exceeds this, >> Postgres will try to run a checkpoint. Under some circumstances it won't, >> but let's keep it simple for now. >> >> wal_keep_size is all about *replication*. Replicas need WAL files to >> stick around for long enough that they can process them. wal_keep_size is >> a minimum figure. >> >> Tom >> On Monday, October 6, 2025 at 03:51:17 PM EDT, Raj < >> rajeshkumar.dba09@gmail.com> wrote: >> >> >> Should Wal_keep_size <= max_wal_size ? >> > --00000000000007fdaa06408a5f2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Note archive mode is enabled.

On Tue= , 7 Oct 2025, 10:22 Raj, <rajeshkumar.dba09@gmail.com> wrote:
If wal_keep_size is more than max_wal_size would= n't it always trigger checkpoint ?

=
On Tue, 7 Oct 2025, 03:08 Thomas Carr= oll, <tomfecarroll@yahoo.com> wrote:
Hope nobody minds me chipping in here.

The answer is "not necessarily.&= quot;=C2=A0 The names make them seem closely related, but not so much.

max_wal_size is all about c= heckpoints.=C2=A0 When the WAL exceeds this, Postgres will try to run a= checkpoint.=C2=A0 Under some circumstances it won't, but let's kee= p it simple for now.

wal_k= eep_size is all about replication.=C2=A0 Replicas need WAL files to = stick around for long enough that they can process them.=C2=A0 wal_keep_siz= e is a minimum figure.

Tom
=20
=20
On Monday, October 6, 2025 at 03:51:17 PM EDT, Raj = <rajeshkumar.dba09@gmail.com> wrote:


=20 =20
Should Wal_keep_size <=3D max_wal_size ?
--00000000000007fdaa06408a5f2d--