Manage
CO.NF for your Blog
Configuration Snippet Parameter Snippet

wal_writer_delay

  1. Documentation
  2. Write-Ahead Log
  3. Settings
  4. wal_writer_delay
COPY SHARING LINK
Type: integer
Default: 200 (200ms)
Min: 1 (1ms)
Max: 10000 (10s)
Unit: milliseconds (ms)
Context: sighup
Restart: false
Time between WAL flushes performed in the WAL writer

Specifies how often the WAL writer flushes WAL, in time terms. After flushing WAL the writer sleeps for the length of time given by wal_writer_delay, unless woken up sooner by an asynchronously committing transaction. If the last flush happened less than wal_writer_delay ago and less than wal_writer_flush_after worth of WAL has been produced since, then WAL is only written to the operating system, not flushed to disk. If this value is specified without units, it is taken as milliseconds. The default value is 200 milliseconds (200ms). Note that on many systems, the effective resolution of sleep delays is 10 milliseconds; setting wal_writer_delay to a value that is not a multiple of 10 might have the same results as setting it to the next higher multiple of 10. This parameter can only be set in the postgresql.conf file or on the server command line.

Official docs

Search in source code

Recommendations

Defines the maximum data (in time) that can be lost if synchronous_commit=off and the database shuts down. Because of long transactions, actual data lost can be up to twice this time. Has no effect if synchronous_commit=on. If you are going to turn synchronous_commit=off server-wide, you should probably lower this to prevent too much data loss.
By annotated.conf

Comments