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?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
