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 1tLchK-00Fwm5-5i for pgsql-admin@arkaria.postgresql.org; Thu, 12 Dec 2024 06:29:18 +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 1tLchH-007x1S-MZ for pgsql-admin@arkaria.postgresql.org; Thu, 12 Dec 2024 06:29:16 +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 1tLce3-007qZ5-Bx for pgsql-admin@lists.postgresql.org; Thu, 12 Dec 2024 06:25:56 +0000 Received: from mail-ot1-x330.google.com ([2607:f8b0:4864:20::330]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tLce1-002OfA-T4 for pgsql-admin@lists.postgresql.org; Thu, 12 Dec 2024 06:25:55 +0000 Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-71e2bb84fe3so131796a34.1 for ; Wed, 11 Dec 2024 22:25:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733984753; x=1734589553; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HhqHVJejktiGVi0M/UtQfMISqlIW5YbUKF9JYpmrijQ=; b=ZzbmQralYfU8DlcqUnemc0pQvWxXfpL8Lt0FT1LmtLdPBdyPk4WyfWtPSFAQD2yWnt N8vUH26C4B/M1ktDRQGxn2vjV53B3kM7D5JX1U6fmskF5aRBsDa8Lg9ntlg4PSk+ZhTs vXsNDxZQ65urWbdLJayYAAuqukjTENrh2ES2xHHG/XQ1I/8QDXpTmpmrCmnUhlmAzTqN HPgrlDf7WReDI19+V9thv/OiRT2GtBTEb0V/6kQV99ojYRO2VvMGeN+Zk81PSCMp4l87 YQ5RIL1ksje7SFA0963tzdKivz89ns/uqYlgOYVlr/QI6yViaZG6xZrVj5TlZ2Odf9Li qeMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733984753; x=1734589553; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HhqHVJejktiGVi0M/UtQfMISqlIW5YbUKF9JYpmrijQ=; b=SA/fNdjH1C/0Hy74PcDV0j0S39epridm9V90iTB0rFlmSznHHbmqwCWqFpwJsouiww lmy9hrbHKtZponS2WMKTE4khIvTXH25Jx5TPXoMzfNSDFbzZHEeKUYDu2D52DOmWkdSO CWrVgbqfIFFbpSDVMH4XvYdDmdek5giilyjHQVS1hsRWFE+Ncpofa0r426ApfiGOj7Qw Jepm7Y3VUKPFnWoF0gGrpr5CABjfA83g8RM1yYHQOn5RsSoDzmqwK6RgWcMhQbMbItU0 axJ6MsrXzEjVKkRWh6GJ5+qbSaGKSu5pUXLHfJlWlsK1jljjn+G+iF3iXPBQpkKQ/gnA OsbA== X-Gm-Message-State: AOJu0YyMa8qCIzwEKXvfgZZQmBI51amuzcrPCe5keLzQ/O6+ewPBw8qB Oazp/O00L5SuIyMxT/NDoeSSJ4ZFUweYnNxqCiQk1g+nYMh/f+ySmLRO/XUZvZWoTjDXBWHba9w J9RSCVe2VsTBlEcau9At95pcYC9Y= X-Gm-Gg: ASbGncscOfC+tMouEp66GOfR1r6Pg6YRI/uxL9gcmCmIsIrGzzGehSiDbLqgEnrSUQX SdEJ6WCW3twhUx1NXrXmG4T1NzlajjiFm43VVgQ== X-Google-Smtp-Source: AGHT+IHA01jvhD+Y54xLK5BsV6MoHSS4FvxVA71bQmkk0cEVazg15ukRY7rik1/mGpXyk6D9dfonklrYXCv6FbVX9UE= X-Received: by 2002:a05:6830:25d4:b0:71d:fdf7:f8da with SMTP id 46e09a7af769-71e29ee69e1mr1101731a34.27.1733984752934; Wed, 11 Dec 2024 22:25:52 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ac9:5d0f:0:b0:577:9519:f64a with HTTP; Wed, 11 Dec 2024 22:25:52 -0800 (PST) In-Reply-To: <155477463.1496353.1733983706261@mail.yahoo.com> References: <155477463.1496353.1733983706261.ref@mail.yahoo.com> <155477463.1496353.1733983706261@mail.yahoo.com> From: "David G. Johnston" Date: Wed, 11 Dec 2024 23:25:52 -0700 Message-ID: Subject: Re: VacuumDB generating huge WAL filed To: SASIKUMAR Devaraj Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000003ea8fa06290cc995" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003ea8fa06290cc995 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, December 11, 2024, SASIKUMAR Devaraj wrote: > > When we are running vacuumdb for our database of 1.5TB it is generating > approximately 60GB of WAL files? Any way we can reduce this WAL file > generation? > > Set a much more aggressive autovacuum so you don=E2=80=99t accumulate as mu= ch dead tuples between runs? David J. --0000000000003ea8fa06290cc995 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, December 11, 2024, SASIKUMAR Devaraj <sashikumard@yahoo.com> wrote:

When we are running vacuumdb for our database of = 1.5TB it is generating approximately 60GB of WAL files? Any way we can redu= ce this WAL file generation?


Set a much more aggressive autovacuum so you don=E2=80=99= t accumulate as much dead tuples between runs?

Dav= id J.
--0000000000003ea8fa06290cc995--