"David F. Skoll" <dfs@xxxxxxxxxxxxxxxxxx> wrote: > shared_buffers = 24MB You should probably set that higher. Different workloads favor different settings, but if you've got any reasonable amount of RAM for a modern machine, somewhere between 256MB and one-third of total RAM is usually best. > archive_command = '/usr/bin/wal_archive_command.pl %p' It would probably be safer to pass in %f, too, and use it for the file name rather than plucking off the last portion of the %p -- at a minimum it might reduce the chances that you'd use that technique in restore_command, where it flat out won't work. > autovacuum = off Be very careful if you choose to do this -- you've just made yourself responsible for preventing bloat which can slowly strangle performance. There are a few setting which should almost always be overridden for production use. You might want to read this for a start: http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server None of those, however, seem likely to cause the problem you describe. Back to blaming the OS. On the other hand, it's possible that tuning these up might change the timings such that you don't hit the OS bug so often. -Kevin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
