From: Simon Riggs Date: Mon, 5 Sep 2016 08:47:49 +0000 (+0100) Subject: Document LSN acronym in WAL Internals X-Git-Tag: REL_10_BETA1~1775 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ec03f4121cec6cf885bf40d9dfb53b8368251e99;p=thirdparty%2Fpostgresql.git Document LSN acronym in WAL Internals We previously didn't mention what an LSN actually was. Simon Riggs and Michael Paquier --- diff --git a/doc/src/sgml/acronyms.sgml b/doc/src/sgml/acronyms.sgml index 38f111ef9d9..bf2273fa8a0 100644 --- a/doc/src/sgml/acronyms.sgml +++ b/doc/src/sgml/acronyms.sgml @@ -380,6 +380,16 @@ + + LSN + + + Log Sequence Number, see pg_lsn + and WAL Internals. + + + + MSVC diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 503ea8a2a7e..9ae65477218 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -724,6 +724,10 @@ WAL Internals + + LSN + + WAL is automatically enabled; no action is required from the administrator except ensuring that the @@ -732,6 +736,18 @@ linkend="wal-configuration">). + + WAL records are appended to the WAL + logs as each new record is written. The insert position is described by + a Log Sequence Number (LSN) that is a byte offset into + the logs, increasing monotonically with each new record. + LSN values are returned as the datatype + pg_lsn. Values can be + compared to calculate the volume of WAL data that + separates them, so they are used to measure the progress of replication + and recovery. + + WAL logs are stored in the directory pg_xlog under the data directory, as a set of