1- <!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.376 2007/04/07 03:34:36 momjian Exp $ -->
1+ <!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.377 2007/04/07 03:58:08 neilc Exp $ -->
22
33 <chapter id="functions">
44 <title>Functions and Operators</title>
@@ -11359,9 +11359,10 @@ postgres=# select pg_start_backup('label_goes_here');
1135911359
1136011360 <para>
1136111361 <function>pg_current_xlog_location</> displays the current transaction log write
11362- location in the same format used by the above functions. Similarly
11362+ location in the same format used by the above functions. Similarly,
1136311363 <function>pg_current_xlog_insert_location</> displays the current transaction log
11364- insertion point. The insertion point is the <quote>logical</> end of transaction log
11364+ insertion point. The insertion point is the <quote>logical</> end
11365+ of the transaction log
1136511366 at any instant, while the write location is the end of what has actually
1136611367 been written out from the server's internal buffers. The write location
1136711368 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());
1138311384(1 row)
1138411385</programlisting>
1138511386 Similarly, <function>pg_xlogfile_name</> extracts just the transaction log file name.
11386- When the giventransction log location is exactly atan transaction log file boundary, both
11387+ When the giventransaction log location is exactly ata transaction log file boundary, both
1138711388 these functions return the name of the preceding transaction log file.
1138811389 This is usually the desired behavior for managing transaction log archiving
1138911390 behavior, since the preceding file is the last one that currently
