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 1taj1y-004UrU-E3 for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 22:17:03 +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 1taj1x-006B85-IW for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 22:17:01 +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 1taj1x-006B7l-6a for pgsql-general@lists.postgresql.org; Wed, 22 Jan 2025 22:17:01 +0000 Received: from mail-wm1-x333.google.com ([2a00:1450:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1taj1u-000z87-2e for pgsql-general@postgresql.org; Wed, 22 Jan 2025 22:17:00 +0000 Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-4361815b96cso1703955e9.1 for ; Wed, 22 Jan 2025 14:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1737584218; x=1738189018; darn=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=9paV0MgQjs+nZvcR8RBBIdIdAUvwFDizB6gZqZdf8xU=; b=C80Z2HctU7IjE/ixYe+GKy942/7QLhneEl7J05EI0iRPSv5NasXCb8TBlNWsrFm8PO 8h+pVYJC/tbTmXEjGKxvjbds2QKhxP3u4bWg1O87PZ2xSsV/+khstm6t/G2Avx6pDtCg JrjKVmdC2T1B6hCFfwvqAp4vfhr+6OKO5HL2LVd/OM7Br26xeiXJwsAMUnBXgcpqPe7t Kpdaru+ZV43vp0liTAalpLY6ZoYYu/THd+0BuWX1VmDnt4R1xNXQr/TyiYKclXOPW60K GgASTRmK0tcHlnhHsi8/omCtDjLuHh8Jh5nLqCFfE8Kjhf+JDW4Zgi6ShO8IfYeBYMAm V6dQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737584218; x=1738189018; 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=9paV0MgQjs+nZvcR8RBBIdIdAUvwFDizB6gZqZdf8xU=; b=esx5ynOwkUovszOCFnlTW/Z3OrsY8fWc5H/B2WLmpks/nkT+BkxzDG2wVvfUKORqsp AAKwvHe+HMIEPW8bvUTOy9UOcsgaCqYXZW2ABf0CY4doSjjoIUOuX5fzVmqXuwL+z7QU Bb2W0jedAqDSsrRCfI0H1WdsaguL5K0I3Xh48UIvDMtUYM/d4u2JbSTGH1QsQwTnUpAW Z1CPYbv0/xEntrO29p7ZdwYYzFf1ixhtqJv8tnqm3kK1APrfG4+i9hrI0CuAEddQNb2C kIHhlNX4+NukdSN6btq9TTDdDfOPwdehJuE4itFYHsueU5vDaZOSv/X7dJYWxjAHBX+H zdFA== X-Forwarded-Encrypted: i=1; AJvYcCVcegha0/CQa1BNmT7gbKXUICEq8DaSkvsx7QhBsCxzfY6Y+ysbQT226iXNJvOTkdhgoxBZJh1GFvo2/C5J@postgresql.org X-Gm-Message-State: AOJu0Yy/ddQWMTx8imJ9eVQKmpZaXCJAoW1Y6vgWbLxVuGiYaGrEbrUz yoaxBscZtn0RkVdrV6RmQYW9r+r0JixPb1xkyB8HZln3S8GrJIz0rBEOLRzHPPU= X-Gm-Gg: ASbGncuFhw+towQW6zh7myp1CaL649Fr0M/VoCcnXuEvCZ0ZxlWBijsA/JDMm2xKmuq 0BJwGLV44T4G3FVaUbuIer0EcPhPNZrVAbUD8otPPcfG6OyAYwxb+IHiL1U16QDw4ySOjeKskBQ T/8ZcHk5ku6qhtIdwUfKfn7tJcMu7HaBvANRTO67KqAZmJqlquGD0aqv1PG3nZCXMb3xKTGgScv cCPKWXLusidTmSnBaFsWk/7xsvxP3LQw2dQbkbkhYZx59/4+ie0oz74BlTGrRk1soJeUVQISuN2 z1N1zLKI3Cok X-Google-Smtp-Source: AGHT+IHE3jqG5AZNb6KlmccZ9i2fPN+26nacbB9YngY9c6Su9bEIZlUAOQFCmBhTlyof82T51FIGfg== X-Received: by 2002:a05:600c:5486:b0:436:51bb:7a52 with SMTP id 5b1f17b1804b1-438913c9c93mr222648135e9.7.1737584217676; Wed, 22 Jan 2025 14:16:57 -0800 (PST) Received: from localhost.localdomain ([2001:871:260:165:bf03:4f26:ad0b:af3]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-438b31c8ac5sm40449125e9.39.2025.01.22.14.16.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Jan 2025 14:16:57 -0800 (PST) Message-ID: <6a22efea7f4649424d6b99d8223f261eec0f717e.camel@cybertec.at> Subject: Re: Return of the pg_wal issue.. From: Laurenz Albe To: Paul Brindusa , pgsql-general Date: Wed, 22 Jan 2025 23:16:56 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2025-01-22 at 17:33 +0000, Paul Brindusa wrote: > So I want to try and get a solution for this and fix this issue with the = pg_wal > files filling up the drive at a ridiculous rate. I have been manually mov= ing > logs to a different directory but have had no luck in finding an actual s= olution. >=20 > The cluster is a 3 node cluster with HA which is running wirth patroni. >=20 > Please help me out, I will mention that I have test cluster spun up in ca= se > something needs testing.=C2=A0 >=20 > Also want to give a shout out to Lorenz Albe's for posting stuff about wa= l > files on his company blog. I guess you are referring to https://www.cybertec-postgresql.com/en/why-does-my-pg_wal-keep-growing/ I listed all the reasons I know for your predicament. Did you do some research along these lines? If yes, what did you find? Yours, Laurenz Albe