From: | Muhammad Imtiaz <imtiazpg712(at)gmail(dot)com> |
---|---|
To: | Sathish Reddy <sathishreddy(dot)postgresql(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pg_repack |
Date: | 2024-08-13 08:15:44 |
Message-ID: | CACW1Ly0wG4MZ+OgAWBDZwPXmNW_--+iWqp3mmru40iu=C8v3aw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
Pg_repack doesn’t use unlogged tables, but you can minimize WAL file 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 PM Sathish Reddy <
sathishreddy(dot)postgresql(at)gmail(dot)com> wrote:
> Hi
> 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 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Domen Šetar | 2024-08-13 09:56:53 | Function problem |
Previous Message | William Sescu (Suva) | 2024-08-13 08:07:04 | No Message "PostgreSQL, contrib, and documentation successfully made. Ready to install." |