From 46052d9ef314deafa8c94ac7fda4a2811db0679e Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 12 May 2017 13:53:24 -0400 Subject: [PATCH] Replace another "transaction log" with "write-ahead log" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reported-by: Dagfinn Ilmari Mannsåker --- doc/src/sgml/func.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 0527641b7cc..5f47c59f8ad 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -18628,7 +18628,7 @@ postgres=# select pg_start_backup('label_goes_here'); pg_current_wal_insert_lsn displays the current write-ahead log insertion location and pg_current_wal_flush_lsn displays the current write-ahead log flush location. The insertion location is the logical - end of the transaction log at any instant, while the write location is the end of + end of the write-ahead log at any instant, while the write location is the end of what has actually been written out from the server's internal buffers and flush location is the location guaranteed to be written to durable storage. The write location is the end of what can be examined from outside the server, and is usually