On 01/31/11 17:13, Tom Lane wrote:
Jeff Ross<jross@xxxxxxxxxx> writes:
In the meantime, I now have 242 16MB files in pg_xlog/. The
archive_status directory in pg_xlog/has a matching .done file for all
but the most recent of those pg_xlog files.
What have you got checkpoint_segments set to?
I had wal_keep_segments *way* too high. I wanted 30 but somehow ended
up with 300.
Here are the rest of my settings in case I missed something else:
#my settings
listen_addresses = 'localhost,10.31.16.2'
unix_socket_directory = '/var/postgresql/'
log_line_prefix = '<%u%%%d> '
log_statement = 'all'
archive_mode = on
wal_level = hot_standby hot_standby
archive_command = '/etc/scripts/wal_archive.sh %p %f'
default_statistics_target = 50 # pgtune wizard 2009-12-19
maintenance_work_mem = 120MB # pgtune wizard 2009-12-19
constraint_exclusion = on # pgtune wizard 2009-12-19
checkpoint_completion_target = 0.9 # pgtune wizard 2009-12-19
effective_cache_size = 1408MB # pgtune wizard 2009-12-19
work_mem = 12MB # pgtune wizard 2009-12-19
wal_buffers = 8MB # pgtune wizard 2009-12-19
checkpoint_segments = 16 # pgtune wizard 2009-12-19
shared_buffers = 480MB # pgtune wizard 2009-12-19
max_connections = 80 # pgtune wizard 2009-12-19
max_wal_senders = 3 # max number of walsender processes
wal_keep_segments = 300
Thanks, Tom!
Jeff
Am I correct in thinking that I can delete most if not all of the
pg_xlog/ files that have a matching .done entry in
pg_xlog/archive_status/ ? Or is there a better way?
The system should be removing them for itself once there are too many.
Trying to remove them manually is a good recipe for creating trouble.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
