Re: wal segment size
| От | Greg Sabino Mullane |
|---|---|
| Тема | Re: wal segment size |
| Дата | |
| Msg-id | CAKAnmm+yoNEQCV3qXceXm9rNoOAPYK0DQCpSqLkNGvGuOQ3W=A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: wal segment size ("Colin 't Hart" <colinthart@gmail.com>) |
| Ответы |
Re: wal segment size
|
| Список | 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
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
В списке pgsql-general по дате отправления: