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 1uoTJy-004TgR-HN for pgpool-general@arkaria.postgresql.org; Tue, 19 Aug 2025 20:52:43 +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 1uoTJy-00Gzjo-1D for pgpool-general@arkaria.postgresql.org; Tue, 19 Aug 2025 20:52:42 +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 1uoTJx-00Gzjg-Ru for pgpool-general@lists.postgresql.org; Tue, 19 Aug 2025 20:52:42 +0000 Received: from mail-pl1-x629.google.com ([2607:f8b0:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uoTJw-000j7g-03 for pgpool-general@lists.postgresql.org; Tue, 19 Aug 2025 20:52:41 +0000 Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-24458298aedso49503255ad.3 for ; Tue, 19 Aug 2025 13:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755636759; x=1756241559; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=AvHTAK0xJg6uFTn+z6XFk10nCk3hQDQpPlhoKdP+Cvg=; b=cmDvXZ7QQ/v+EcvpJzbIYHy+2kKrDMM3GLrt9R2KpariGxggjo+oW2RHM/E5k+uTlR 7dxa6tv0WQ4WtzFN+HSAd+Z87vEjRmtC8PBO08ad556+QLPYqbKsQBAHW0P1+u2tj+v4 yVO+PqxqFRnTtv1HuTEgiY9bJodaNWqPk7krhvldOD3Uhvk7G+WPkKC7C47DWxxBxwqS jbmRSQ0iCJh9wwYFRRe89iX7m+2ImCav8OToo0GNmGJLDkv1/hS/t65GwvPbfDC6FDuD 22N3AQHHXoMSlltUUvmS2mSZjHVbMYI4qY2/e0PKCyJH+ytBGkGw6mPMvFfWlaO7YX51 inGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755636759; x=1756241559; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=AvHTAK0xJg6uFTn+z6XFk10nCk3hQDQpPlhoKdP+Cvg=; b=T6SFrYyiXuygf9QekuOyWBMT4ItOdJ23q7Jwrr+qYTgRMgTXB07N0lnl5PmlqO0o6d Y+uG7q7IzQ1NF3mOAouWJD7Qgu+nn1ll0nZjDY3+r4zmut0zWm+Y/PH2YHroUdYS6+Kj xrGJ4mqBltmGwkz3AWRl0S3/50HPHKMLhUdIQqCyAAOnluaPdoi+WaKb9Ci7Au6b5twy pTgIkRawvQniDCZ07Swm/woSGX5xOoDcdOrRQXGhbdfEby8VXQPeUapQDMMnHheGVnW9 X5i7m0KHAuqIkPM/Sw2F38/hJ3VaAlqmgm89Qb3/vQtCDKrtInFU+jIhjaOu1T5kG+yC uFwQ== X-Gm-Message-State: AOJu0YxCwr05Glu9n7k/H+nX/w3z+sKIl44DcosQ0Ejwu/oUCoQtQ8lZ YmqHd+NP65PKpJmQurRcciubiI6smWKqlYhWgMSNpy46q4t1xcyxyHredyFN0Diqu6qLgSUD5Tf odUD4HDbbYxziovGyhoI8x1GK8CaZausMwkQBjhs= X-Gm-Gg: ASbGncvZawgywPvI5BSTIaRHJLmqUuMGkAS+wmkGqT4JHYcURGCvLPYsDM24sZX0YbQ N996FxffMc6HNA94A5VfnIO7Qy69XlNjbOy3nBKBXeY05aNBKB9d+gN+FRRL8d8sFn0buIQzxLk iLc16oSO8dSPCVSDuGmXIU1Pk0ne3w1pUqZq3t60q7eaUCitf5dANTcyVWwAfo523fKxFhB3Ibd TIO X-Google-Smtp-Source: AGHT+IFyklpOzu5ecJlAa9Y4qp75tD/fXKCfh/+6CedCIwXRQQOiDlUNMj+GGcX/Uex6AKZdfAsczUIVu6Wna9rgJq4= X-Received: by 2002:a17:902:ea04:b0:243:a16:18f2 with SMTP id d9443c01a7336-245ef113db1mr4569375ad.11.1755636759259; Tue, 19 Aug 2025 13:52:39 -0700 (PDT) MIME-Version: 1.0 From: Daniel Cifuentes Date: Tue, 19 Aug 2025 15:52:22 -0500 X-Gm-Features: Ac12FXz3JjTERY3lrP_3GIbZktarA3PQOJEonpJvMsR7koEZAP300mjgRtYePNQ Message-ID: Subject: Delete archived WALs on PRIMARY NODE To: pgpool-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000063ecd5063cbe0997" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000063ecd5063cbe0997 Content-Type: text/plain; charset="UTF-8" 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 the replication is ok. I have read about the pg_archivecleanup command but the documentation says 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. --00000000000063ecd5063cbe0997 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 the re= plication is ok.
I have read about the=C2=A0pg_archi= vecleanup=C2=A0command but the documentation says that the command is desig= ned for standby servers (PostgreSQL: Documentation: 16: pg_archivecleanup).
What I have noticed is that Pgpool 4.5.4 documentation ind= icates:
A= rchive modeon/var/lib/p= gsql/archivedir
Pgpool-II + Watchdog Set= up Example

While 4.6.2 version says:
=
Archive mode= off
Pgpool-II + Watchdo= g Setup Example

So a solution would be doing an upgrade and sett= ing off the archive mode? Is that the best solution?=C2=A0
Thank = you in advance for your help.
--00000000000063ecd5063cbe0997--