From 64ee1a8a55d3e34f2170e67258cc8ad0d2f4ee95 Mon Sep 17 00:00:00 2001 From: Neil Conway Date: Sat, 7 Apr 2007 03:58:08 +0000 Subject: [PATCH] Fix a few typos in the docs. --- doc/src/sgml/func.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 64af03fbdc..b7023dde4a 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,4 +1,4 @@ - + Functions and Operators @@ -11359,9 +11359,10 @@ postgres=# select pg_start_backup('label_goes_here'); pg_current_xlog_location displays the current transaction log write - location in the same format used by the above functions. Similarly + location in the same format used by the above functions. Similarly, pg_current_xlog_insert_location displays the current transaction log - insertion point. The insertion point is the logical end of transaction log + insertion point. The insertion point is the logical end + of the transaction log at any instant, while the write location is the end of what has actually been written out from the server's internal buffers. The write location is the end of what can be examined from outside the server, and is usually @@ -11383,7 +11384,7 @@ postgres=# select * from pg_xlogfile_name_offset(pg_stop_backup()); (1 row) Similarly, pg_xlogfile_name extracts just the transaction log file name. - When the given transction log location is exactly at an transaction log file boundary, both + When the given transaction log location is exactly at a transaction log file boundary, both these functions return the name of the preceding transaction log file. This is usually the desired behavior for managing transaction log archiving behavior, since the preceding file is the last one that currently -- 2.39.5