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 1uol3p-009fYm-02 for pgpool-general@arkaria.postgresql.org; Wed, 20 Aug 2025 15:49:14 +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 1uol3o-009PAq-6P for pgpool-general@arkaria.postgresql.org; Wed, 20 Aug 2025 15:49:12 +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 1uol3n-009PAh-T6 for pgpool-general@lists.postgresql.org; Wed, 20 Aug 2025 15:49:12 +0000 Received: from mail-pg1-x531.google.com ([2607:f8b0:4864:20::531]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uol3m-000rvM-08 for pgpool-general@lists.postgresql.org; Wed, 20 Aug 2025 15:49:11 +0000 Received: by mail-pg1-x531.google.com with SMTP id 41be03b00d2f7-b471756592cso4492025a12.3 for ; Wed, 20 Aug 2025 08:49:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755704950; x=1756309750; 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=/PsrtaS3aPhIGyFQyVk01ARxXDFqCvY1ZPSJrxNpOvk=; b=gb7zNjD6O1Y74di1zQo1McSRSA2biU251p6fumu/cpypQiFIVxO5w4Jha3LN/Fsj7/ 7ROzdAPav8Og4f/FmBdy1tXI7UFoKgqtLxdqEgdUtovlQOIhgzfiW5u4lMYhBQ0Sa7GS kLyKPj59N2uXdoHGzcagkfNnMBJz3qrML4PdfoCADk/J20ykeHJ5R+CPN8LIJmMZXUC/ 7cPoo8KvrdzPqS3j7TjQbn61+1YKykCQyuZO3reF0QJTQbFjiHP24g/eBqTPrPEMJ6QO H45+mbOhFvH89k3kjlNWjW8baSZyDblAjPf3KEiL9AS5ZLR1yxvWbvlFrGp3wAaIdKSZ lzxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755704950; x=1756309750; 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=/PsrtaS3aPhIGyFQyVk01ARxXDFqCvY1ZPSJrxNpOvk=; b=oA2sewUZUN+c6cvzLfjUkYQMPjYvv7VE59uYhPa0bnIjREv7f4Y34Goxb4U2NEfObK wpWg1L9vUOMIbpIALnMvwXMEAFP3/nOGWKE/OGB71MYdlz7/oJiv59ebLkb7i/AHVKk2 Rj44y9DumBtok3APNRbYY6T7BmEoxu8vrPwZMpRnXnqAYJJvIUra+mLgp3z4W2skaU6p c8EdiElEgBp+qhOPfXHseUT++oqqNpKoLeGU/3a6FonDv3uNyHSpuWYuuQl0Cyo4/6qK 7i+25b2ofduZt0c7RQfz9VLsOmWDT3MmQnEFx4I55OKKgLmsRQ6d4+uV09EM82gnw/r0 HviQ== X-Gm-Message-State: AOJu0YyDVv7wmj7hfRFY2yt3FW0pVJYp+xIIjbmEGy2QWeJ3a7qlccLq pdHNIiRwGWhU4mEU+kSqxfM7/g8C3RoPLFIOEjvA/M1BD2XiCkkus7mTK4KgtrgdrEnfGNM5k8T tqjlo7SZQU5gBH3NmahfNxa6IEn6DzKjwXYXAIaoxMVavAEfsTALxKS0+RVohKMbvuqUdRpU= X-Gm-Gg: ASbGnct2X8TfFWrggURU6hJ8R6Uhv3TvmWd9WeqaRgn1tuErLdoX8x1q/VSfVdMl1wT XT5ihci/MLKvjZGql+LMrGdSQU4BCbXpLMoJH7t4F+hA0KVyMr48ic7dtOUJF0AtnTHiMHB72KT vR5AgZ1vWMonhuyqQ70irhkc4ejHPfPxVtpKFsan91KuFSHXjBjL/ZQAqBqclfMfVNVRFUWD+H2 d9iDT7f/7DItL/89lw= X-Google-Smtp-Source: AGHT+IEvCfd3Vmv2e6U2npFydzSW/vhgG8mXTDxBSIWENSYEFbB+yGEZFGbUVwxGCXq/ItUXwqHDGf9BTrrWGWMGAmQVcwyNadQbZpVX X-Received: by 2002:a17:902:fc83:b0:240:7247:f738 with SMTP id d9443c01a7336-245ef0eee42mr35138545ad.1.1755704949396; Wed, 20 Aug 2025 08:49:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Daniel Cifuentes Date: Wed, 20 Aug 2025 10:48:56 -0500 X-Gm-Features: Ac12FXwZ9vkU4AFiaA7kUiZsYk3tkoSSLSm3a954g6U7wY1hMY1KvM5o_ldM188 Message-ID: Subject: Re: Delete archived WALs on PRIMARY NODE To: Bo Peng Cc: "pgpool-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000d6d8ca063ccde953" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d6d8ca063ccde953 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =F0=9F=91=8D Daniel Cifuentes reaccion=C3=B3 a trav=C3=A9s de Gmail El mi=C3=A9, 20 ago 2025 a las 4:15, Bo Peng () escrib= i=C3=B3: > Hi, > > > So a solution would be doing an upgrade and setting off the archive > mode? Is that the best solution? > > Thank you in advance for your help. > > Upgrade is not necessary. > > You can disable archive_mode in PostgreSQL and modify the follow_primary > and online_recovery scripts to disable archive_mode. > > --- > Bo Peng > SRA OSS K.K. > TEL: 03-5979-2701 FAX: 03-5979-2702 > Mobile: 080-7752-0749 > URL: https://www.sraoss.co.jp/ > > > ________________________________________ > =E5=B7=AE=E5=87=BA=E4=BA=BA: Daniel Cifuentes > =E9=80=81=E4=BF=A1: 2025 =E5=B9=B4 8 =E6=9C=88 20 =E6=97=A5 (=E6=B0=B4=E6= =9B=9C=E6=97=A5) 5:52 > =E5=AE=9B=E5=85=88: pgpool-general@lists.postgresql.org < > pgpool-general@lists.postgresql.org> > =E4=BB=B6=E5=90=8D: Delete archived WALs on PRIMARY NODE > > > > > > > > > > > > Hello, I have a cluster with > Postgres 16.4 > Pgpool-II 4.5.4 > The problem that I am having is that the directory for archives is gettin= g > full with all the old archives. I have done some testing and proved that > the replication is ok. > I have read about the pg_archivecleanup command but the documentation say= s > that the command is designed for standby servers (PostgreSQL: > Documentation: 16: pg_archivecleanup). > > > What I have noticed is that Pgpool 4.5.4 documentation indicates: > > > Archive mode > on > /var/lib/pgsql/archivedirPgpool-II + Watchdog Setup Example > > > While 4.6.2 version says: > > > Archive mode > offPgpool-II + Watchdog Setup Example > > So a solution would be doing an upgrade and setting off the archive mode? > Is that the best solution? > Thank you in advance for your help. > --000000000000d6d8ca063ccde953 Content-Type: text/vnd.google.email-reaction+json; charset="UTF-8" Content-Transfer-Encoding: quoted-printable { "emoji": "=F0=9F=91=8D", "version": 1 } --000000000000d6d8ca063ccde953 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=F0=9F=91=8D<= /p>

Daniel Cifuentes reaccion= =C3=B3 a trav=C3=A9s de Gmail


El mi=C3=A9, 20 ago 2025 a= las 4:15, Bo Peng (<pengbo@sraos= s.co.jp>) escribi=C3=B3:
Hi,=

> So a solution would be doing an upgrade and setting off the archive mo= de? Is that the best solution?=C2=A0
> Thank you in advance for your help.

Upgrade is not necessary.

You can disable archive_mode in PostgreSQL and modify the follow_primary an= d online_recovery scripts to disable archive_mode.

---
Bo Peng <pengbo= @sraoss.co.jp>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
Mobile: 080-7752-0749
URL: https://www.sraoss.co.jp/


________________________________________
=E5=B7=AE=E5=87=BA=E4=BA=BA: Daniel Cifuentes <daercimi@gmail.com>
=E9=80=81=E4=BF=A1: 2025 =E5=B9=B4 8 =E6=9C=88 20 =E6=97=A5 (=E6=B0=B4=E6= =9B=9C=E6=97=A5) 5:52
=E5=AE=9B=E5=85=88: pgpool-general@lists.postgresql.org <pgpool-general@= lists.postgresql.org>
=E4=BB=B6=E5=90=8D: Delete archived WALs on PRIMARY NODE











Hello, I have a cluster with
Postgres 16.4
Pgpool-II 4.5.4
The problem that I am having is that the directory for archives is getting = full with all the old archives. I have done some testing and proved that th= e replication is ok.
I have read about the=C2=A0pg_archivecleanup=C2=A0command but the documenta= tion says that the command is designed for standby servers (PostgreSQL: Doc= umentation: 16: pg_archivecleanup).


What I have noticed is that Pgpool 4.5.4 documentation indicates:


Archive mode
on
/var/lib/pgsql/archivedirPgpool-II + Watchdog Setup Example


While 4.6.2 version says:


Archive mode
offPgpool-II + Watchdog Setup Example

So a solution would be doing an upgrade and setting off the archive mode? I= s that the best solution?=C2=A0
Thank you in advance for your help.
--000000000000d6d8ca063ccde953--