| From: | Francisco Reyes <lists(at)natserv(dot)net> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Large pg_xlog |
| Date: | 2016-09-26 23:52:26 |
| Message-ID: | fd070ae7-9977-bb40-afa9-7723ba81254d@natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Postgresql 9.3
checkpoint_segments=6
wal_keep_segments=300
Machine is master for 2, asynchronous, slaves.
pg_xlog in /var/lib/postgresql/9.3/main/pg_xlog
NFS mount with WAL archiving in /opt/backups/walarchives/HostName
During a load of a file, using copy, the pg_xlog grew to almost 120GB
and one of the slaves fell behind (at another data center). Since I am
not using replication slots I expected WAL to be wall_keep_segments x
16MB = 4GB. Any idea why it grew so large?
Once I rsync wal archives to the slave and it catches up then WAL goes down.
Any ideas why pg_xlog is going so high?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2016-09-27 00:08:06 | Re: Large pg_xlog |
| Previous Message | David G. Johnston | 2016-09-26 23:34:56 | Re: bitwise storage and operations |