From: | Prince Pathria <prince(dot)pathria(at)goevive(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | WAL segments held for replcation |
Date: | 2018-09-21 21:11:56 |
Message-ID: | CAON0DawEmb-cBqBwzk2-dXgvVqNa137sZsqJXPmuTAWH_BGPGQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I have following config
wal_buffers = 16MB
min_wal_size = 1GB
max_wal_size = 2GB
synchronous_commit = on
archive_mode = on
archive_command = 'cp %p /opt/postgres/%f'
max_wal_senders = 4
wal_keep_segments = 1024
synchronous_standby_names = 'pgslave01'
1. Can we raise wal segment size to more than 16MB and is it same as
`wal_buffers` ?
2. During data loading I'm pushing 4GB data, and taking an assumption that
my network is slow,
Will master keep the segments in pg_wal more than wal_keep_segment value
such that it's pulled by standby nodes or it will wipe if off?
3. 1024 wal_keep_segments of 16 mb each makes 16GB of segments kept but I
have kept max_wal_size = 2GB. Which one will be prioritised max_wal_size or
wal_keep_segment?
Thanks!
Prince Pathria
Systems Architect Intern Evive +91 9478670472 goevive.com
From | Date | Subject | |
---|---|---|---|
Next Message | Prince Pathria | 2018-09-23 12:13:34 | Archive clean up command in recovery.conf |
Previous Message | Andres Freund | 2018-09-21 16:26:24 | Re: How to avoid the XLog Write to be the performance bottleneck |