Re: wal segment size - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: wal segment size
Date
Msg-id CAKAnmm+yoNEQCV3qXceXm9rNoOAPYK0DQCpSqLkNGvGuOQ3W=A@mail.gmail.com
Whole thread Raw
In response to Re: wal segment size  ("Colin 't Hart" <colinthart@gmail.com>)
Responses Re: wal segment size
List pgsql-general
On Wed, Dec 17, 2025 at 11:10 AM Colin 't Hart <colinthart@gmail.com> wrote:
Thanks Laurenz, that confirms what I was assuming. Archiving is via pgbackrest to a backup server, over SSH. Approx 750ms to archive each segment is crazy -- I'll check compression parameters too.

Switch to archive-async = on. When doing that, the typical time drops to 10ms or less. Also use a compress-type of lz4 or zst, which perform way better than the default gz. If you are encrypting, that's a bottleneck you just have to deal with, no shortcuts there. :)

tl;dr try other things before messing with the WAL size. The current size can work very well even on very large and very, very busy systems.

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-general by date:

Previous
From: Thiemo Kellner
Date:
Subject: Record last SELECT on a row?
Next
From: Ron Johnson
Date:
Subject: Re: wal segment size