Re: increasing the default WAL segment size

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

To: Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2016-09-20T18:49:04Z

Lists: pgsql-hackers

On 8/24/16 9:31 PM, Robert Haas wrote:
> I'd like to propose that we increase the default WAL segment size,
> which is currently 16MB.

While the discussion about the best default value is ongoing, maybe we
should at least *allow* some larger sizes, for testing out.  Currently,
configure says "Allowed values are 1,2,4,8,16,32,64.".  What might be a
good new upper limit?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make WAL segment size configurable at initdb time.
- fc49e24fa69a 11.0 landed
Perform only one ReadControlFile() during startup.
- 8356753c212a 11.0 landed
Introduce BYTES unit for GUCs.
- 6e7baa322773 11.0 landed
Remove useless duplicate inclusions of system header files.
- 9e3755ecb2d0 10.0 cited
Refactor other replication commands to use DestRemoteSimple.
- bbd8550bce14 10.0 landed
Add a SHOW command to the replication command language.
- d1ecd539477f 10.0 landed
Add a new DestReceiver for printing tuples without catalog access.
- a84069d93504 10.0 landed
Support fls().
- 4f658dc851a7 9.2.0 cited
Extend yesterday's patch making BLCKSZ and RELSEG_SIZE configurable to also
- cf9f6c8d8e9d 8.4.0 cited
Commit the reasonably uncontroversial parts of J.R. Nield's PITR patch, to
- c3c09be34b6b 8.0.0 cited
XLOG (also known as WAL -:)) Bootstrap/Startup/Shutdown.
- 47937403676d 7.1.1 cited
Transaction log manager core code.
- 30659d43eb73 7.1.1 cited