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 1t6UxD-00DOc9-37 for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 13:11:11 +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 1t6UxB-001FaW-D4 for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 13:11:09 +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 1t6UxB-001FaN-2H for pgsql-general@lists.postgresql.org; Thu, 31 Oct 2024 13:11:09 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t6Ux8-0040Fy-Vq for pgsql-general@postgresql.org; Thu, 31 Oct 2024 13:11:08 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-a9a0472306cso118524466b.3 for ; Thu, 31 Oct 2024 06:11:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=cybertec.at; t=1730380265; x=1730985065; 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=CN+OgJWDOWyIuKVmCyIW6iNXZ5z1OaBQtoADAW9QEOI=; b=GLWXvfwe4u8lhG7fBom1nYFW+EcVdWXFwaP169gXLXQ9rPNckxB7pqdOXZQW9lvViu P8W2+CqflHaAK+FLAo1T11N51SVXp4qYz/tYPmWxQPi6W1idKN5McOLqNhHUeXJIM307 EeYBHJ7fMEMnW+vs/ZB4BztlZ4qzPQ/1WZEjA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730380265; x=1730985065; 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=CN+OgJWDOWyIuKVmCyIW6iNXZ5z1OaBQtoADAW9QEOI=; b=Euf08cg+odC+DhYdnOYjhC5S+N9mWbZycG/JT6ReXqzpFmnuEDxxGP/GvW1RDEFIRO 7eJXWpafxZqO6I9gcJrRB5Qw55F1QAYFzVeDY1YQZUhH12cjrnqDyIpP7NZpdvkGtNfg VzQxIVYt2nVJiqxt3m1N1V2nG2m0E4QwNwp2ZMvcUo3Mc5Hc8vswqRThe0+/sZ6Ennyb 2UKsd9hyLgDjPqXVR1oaJN/uG7fxuLF3w8BtTxpVSXGnyN3kZmSdaBEQfV9S7Lr0rySe cD2B2rhG8QYG7ArJJXghSEmh0MTgzsVE07JKyobcLyvPSdsrtSTcsDhQd/pipweJwI9J Y9nQ== X-Forwarded-Encrypted: i=1; AJvYcCUwKpQMSmR5xcKiWN4qan5aqTK0q8QKpf0MlT4+36OqOs8CPRZ1hCM2Ru04++5xzZAcSApBwH/zg+CpPMYP@postgresql.org X-Gm-Message-State: AOJu0Yza8Evqy2eoHE5wKIUjrBU+YSpgOMplGzj0CKrScDKBMzjrtj8Z /nf4JKu40dk9D79llgKriXqq9V+q/IUxeRLXlWRfZ4m+Gs8XXYBeaIMCGeEJGz0= X-Google-Smtp-Source: AGHT+IE+/YYyDCkhn3IV89hClmMpE7nK5C9oQdQX2h5dnalOforwSN72Uu8RdoAANJ0DWJLgevJh4w== X-Received: by 2002:a17:907:3f83:b0:a9a:6633:3a90 with SMTP id a640c23a62f3a-a9e508ac3c0mr278246066b.8.1730380265077; Thu, 31 Oct 2024 06:11:05 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:99b5:1ed4:1131:724f:8ba6]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a9e56494428sm67716766b.25.2024.10.31.06.11.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 31 Oct 2024 06:11:04 -0700 (PDT) Message-ID: <607f4ee059f7d7520f420ddd30fdf2405355f5b0.camel@cybertec.at> Subject: Re: pg_wal folder high disk usage From: Laurenz Albe To: Paul Brindusa , pgsql-general Date: Thu, 31 Oct 2024 14:11:04 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2024-10-31 at 10:36 +0000, Paul Brindusa wrote: > On one of our postgres instances we have the pg_wal/data folder up to 196= GB, out of 200GB disk filled up. > This has stopped the posgresql.service this morning causing two applicati= ons to crash. > Unfortunately our database admin is on leave today, and we are trying to = figure out how to get the disk down? > Any ideas or suggestions are more than welcome. Check why pg_wal is growing: https://www.cybertec-postgresql.com/en/why-does-my-pg_wal-keep-growing/ Yours, Laurenz Albe