История изменений

Обычно линейный лог быстро превышает пределы доступной оперативной памяти

Хм. А вот тут http://www.postgresql.org/docs/9.1/static/wal-configuration.html пишут иначе:

There will always be at least one WAL segment file, and will normally not be more than (2 + checkpoint_completion_target) * checkpoint_segments + 1 or checkpoint_segments + wal_keep_segments + 1 files. Each segment file is normally 16 MB (though this size can be altered when building the server). You can use this to estimate space requirements for WAL. Ordinarily, when old log segment files are no longer needed, they are recycled (renamed to become the next segments in the numbered sequence). If, due to a short-term peak of log output rate, there are more than 3 * checkpoint_segments + 1 segment files, the unneeded segment files will be deleted instead of recycled until the system gets back under this limit.

То есть ожидаемый суммарный размер файлов - 160 Mb. Не смертельно для машины с 2+ Гб оперативы.

Обычно линейный лог быстро превышает пределы доступной оперативной памяти

Хм. А вот тут http://www.postgresql.org/docs/9.1/static/wal-configuration.html пишут иначе:

There will always be at least one WAL segment file, and will normally not be more than (2 + checkpoint_completion_target) * checkpoint_segments + 1 or checkpoint_segments + wal_keep_segments + 1 files. Each segment file is normally 16 MB (though this size can be altered when building the server). You can use this to estimate space requirements for WAL. Ordinarily, when old log segment files are no longer needed, they are recycled (renamed to become the next segments in the numbered sequence). If, due to a short-term peak of log output rate, there are more than 3 * checkpoint_segments + 1 segment files, the unneeded segment files will be deleted instead of recycled until the system gets back under this limit.

То есть ожидаемый размер файлов - 160 Mb. Не смертельно для машины с 2+ Гб оперативы.