Re: increasing the default WAL segment size
David Steele <david@pgmasters.net>
On 3/24/17 12:27 AM, Peter Eisentraut wrote: > On 3/23/17 16:58, Stephen Frost wrote: >> The backup tools need to also get the LSN from the pg_stop_backup and >> verify that they have the WAL file associated with that LSN. > > There is a function for that. > >> They also >> need to make sure that they have all of the WAL files between the >> starting LSN and the ending LSN. Doing that requires understanding how >> the files are named to make sure there aren't any missing. > > There is not a function for that, but there could be one. A function would be nice, but tools often cannot depend on the database being operational so it's still necessary to re-implement them. Having a sane sequence in the WAL makes that easier. -- -David david@pgmasters.net
Commits
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