| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| 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-12 15:48:44 |
| Message-ID: | 202408121548.x5qz5npcikiw@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2024-Aug-12, Sathish Reddy 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.
I bet you'll find that pg_squeeze gives you better characteristics on
those aspects. In any case, it's better if you can find a way to avoid
running either of these tools in a regular manner, and instead treat
them as if they were an emergency solution only, and rely on a better
configured autovacuum to avoid having to schedule them regularly.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-08-12 16:06:27 | Re: Pg_repack |
| Previous Message | manish yadav | 2024-08-12 11:57:29 | Re: Data comparison |