The amount of shared memory used for WAL data that has not yet been written to disk. The default setting of -1 selects a size equal to 1/32nd (about 3%) of shared_buffers, but not less than
64kB nor more than the size of one WAL segment, typically
16MB. This value can be set manually if the automatic choice is too large or too small, but any positive value less than
32kB will be treated as
32kB. If this value is specified without units, it is taken as WAL blocks, that is
XLOG_BLCKSZ bytes, typically 8kB. This parameter can only be set at server start.
The contents of the WAL buffers are written out to disk at every transaction commit, so extremely large values are unlikely to provide a significant benefit. However, setting this value to at least a few megabytes can improve write performance on a busy server where many clients are committing at once. The auto-tuning selected by the default setting of -1 should give reasonable results in most cases.
- Re: Support logical replication of DDLs
- Re: How about a psql backslash command to show GUCs?
- Proposal: Allow walsenders to send WAL directly from wal_buffers to replicas
- Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
- Re: Improve WALRead() to suck data directly from WAL buffers when possible