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 1sdmhD-000usZ-G0 for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 08:15:59 +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 1sdmhC-002XkN-3C for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 08:15:58 +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 1sdmhB-002XkF-OH for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 08:15:57 +0000 Received: from mail-qk1-x72f.google.com ([2607:f8b0:4864:20::72f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdmh9-004VZA-30 for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 08:15:56 +0000 Received: by mail-qk1-x72f.google.com with SMTP id af79cd13be357-7a1d0dc869bso316537985a.2 for ; Tue, 13 Aug 2024 01:15:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723536954; x=1724141754; 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=XomKR9h9gZFzlxiATR9nE1GHXYuC4PhaXqyiVoYKeXQ=; b=i39FW4gRjAVxDZLSRO32bNjwHzwrNiNRTCZB2sL1fnbgNSvy1cdK+Iniwu+PJukCYF 4quJl0EDzp4Ru61mf+zJBp6eJBN3jqptDuLNX9ybC979TGf7XP7AmR4QVEo4V9WVmCvT vpJgM9wDjqDk52Ao9rrzgD6T3XITmzMh3fha7jwcUtx5tiOrYqTbEMGyVCgiec5chGuC v0tU00QimJbmQBjGdhl7g05hUF1xYzS7LSzstk4/OVXVs8heoySTEXjE4bxav2x1RrMW zm6V1mSq5ThBF9nH3t9G7OsuM90Zcrd1twR/uAWRz1DXje766VdlPqKIfCo8naLyk+5l h8rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723536954; x=1724141754; 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=XomKR9h9gZFzlxiATR9nE1GHXYuC4PhaXqyiVoYKeXQ=; b=hVvPWruCEQQ+x5S7OuwGwDFrRwyzF59uCBM5q32H3TJLxrSCyEiZ4OEgxt2Oc59wpC K7brWJr/rN/KIgsw9pvZA2wErOltshnFNb7DbHPKmEf2aT/WBteJWMNFNwg1yYI+Nppr Xqb+oJOVUr/mqo9lsCo1BDERY8aQ0+DOg0Wq7kcOKXao4fnSv+5rLuuQnO687Vc1iiH6 rOPZZoR3Shn4Mk9bWIMQoAHS8pcii51atQtBPakl9VBlGGzQSFSpDVt6P+luVd3r6Fxl zR8puuX5+X++JnEy3d/HO6js0D+U30VNrrYjdgtFe1BhVFvKxTxpx+iKMjULa+yV4UZG E/EQ== X-Gm-Message-State: AOJu0YxuzsxCWKGic1Q5AFNK6Dznzu1bft6tKUDemmVoUS0GdgTsPFWa JeqB5S3VOvTzNovX+7VXONjOdfYE2Yv3Mr4tEgdbC8F6QfpG4XVAlmA6JdAwJ4Fvup8jYdHgfDT O5QXizCcsL7l2BIdsxFEuYjlp/wg= X-Google-Smtp-Source: AGHT+IF0meCNg2hIy4qGHjpz5TVIhwm8dLrZ0r1iLBOadt91GzrgPN0VyO4nCtMzR27w921wmPwwhLVlwJT3kxosqq8= X-Received: by 2002:a05:6214:3f8f:b0:6b2:cf9e:866 with SMTP id 6a1803df08f44-6bf4f79decdmr39313186d6.4.1723536954078; Tue, 13 Aug 2024 01:15:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Imtiaz Date: Tue, 13 Aug 2024 13:15:44 +0500 Message-ID: Subject: Re: Pg_repack To: Sathish Reddy Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e7bcc4061f8c376b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e7bcc4061f8c376b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Pg_repack doesn=E2=80=99t use unlogged tables, but you can minimize WAL fil= e size by enabling wal_compression in postgresql.conf. Additionally, you can fine-tune wal_buffers, checkpoint_timeout, and checkpoint_completion_target to better manage WAL file size. Regards, Muhammad Imtiaz On Mon, Aug 12, 2024 at 4:48=E2=80=AFPM Sathish Reddy < sathishreddy.postgresql@gmail.com> wrote: > Hi > We have configure pg_repack on database.when we ran pg_repak it is usin= g > temporary table on repack once repack done it is going to swap temporary > table to original .on these case it is genarate huse wal files and it > getting size increase be end . > > We need help on these instead of using temporary table can we use > unlog table on reduce these wal case. > > > Thanks > Sathishreddy > --000000000000e7bcc4061f8c376b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Pg_repack doesn=E2=80=99t use unlogged tables, = but you can minimize WAL file size by enabling wal_compression in postgresq= l.conf. Additionally, you can fine-tune wal_buffers, checkpoint_timeout, an= d checkpoint_completion_target to better manage WAL file size.

Regar= ds,
Muhammad Imtiaz

On Mon, Aug 12, 2024 at 4:48=E2=80=AFPM Sathish Reddy= <sathishreddy.post= gresql@gmail.com> wrote:
Hi=C2=A0
=C2=A0 We have = configure pg_repack on database.when we ran pg_repak it is using temporary = table on repack once repack done it is going to swap temporary table to ori= ginal .on these case it is genarate huse wal files and it getting size incr= ease be end .=C2=A0
=C2=A0 =C2=A0
=C2=A0 =C2=A0 We need help on these instead of using temporary table c= an we use unlog table on reduce these wal case.

=

Thanks=C2=A0
Sathishreddy=C2=A0
--000000000000e7bcc4061f8c376b--