diff options
| -rw-r--r-- | doc/src/sgml/install.sgml | 10 | ||||
| -rw-r--r-- | doc/src/sgml/legal.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/notation.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/release.sgml | 20 | ||||
| -rw-r--r-- | doc/src/sgml/syntax.sgml | 2 |
5 files changed, 24 insertions, 14 deletions
diff --git a/doc/src/sgml/install.sgml b/doc/src/sgml/install.sgml index c1023a5bec7..33ae9547c49 100644 --- a/doc/src/sgml/install.sgml +++ b/doc/src/sgml/install.sgml @@ -719,14 +719,16 @@ pg_id: can't load library 'libpq.so' <Step Performance="required"> <para> Several regression tests could fail if the user's locale collation - scheme is different from that of standard C locale. + scheme is different from that of the standard <literal>C</literal> locale. </para> <para> If you configure and compile <ProductName>Postgres</ProductName> - with the <option>--enable-locale</option> option then - set locale environment to C (or unset all LC_* variables) + with <option>--enable-locale</option> then you should + set the locale environment to <quote><literal>C</literal></quote> + (or unset all <quote>LC_*</quote> variables) by putting these additional lines to your login environment - before starting postmaster: + before starting <application>postmaster</application>: + <ProgramListing> LC_COLLATE=C LC_CTYPE=C diff --git a/doc/src/sgml/legal.sgml b/doc/src/sgml/legal.sgml index 8078fa3433c..cc6e7807c57 100644 --- a/doc/src/sgml/legal.sgml +++ b/doc/src/sgml/legal.sgml @@ -1,4 +1,4 @@ -<sect1> +<sect1 id="copyright"> <title>Copyrights and Trademarks</title> <para> diff --git a/doc/src/sgml/notation.sgml b/doc/src/sgml/notation.sgml index 712ebd1832d..b33034a1fcb 100644 --- a/doc/src/sgml/notation.sgml +++ b/doc/src/sgml/notation.sgml @@ -1,4 +1,4 @@ -<sect1> +<sect1 id="terminology"> <title>Terminology</title> <para> @@ -65,7 +65,7 @@ </para> </sect1> -<sect1> +<sect1 id="notation"> <title>Notation</title> <para> diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 2e7732a0899..1d3f2c661ea 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,4 +1,4 @@ - <chapter> + <chapter id="release"> <title>Release Notes</title> <sect1> @@ -44,10 +44,18 @@ longer are restricted by simple table-level locking; we have something better than row-level locking. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term> + Hot backups from <application>pg_dump</application> + </term> + <listitem> <para> - Another big benefit of MVCC is that <application>pg_dump</application> - can now generate consistent backups of live, active databases, without - blocking active transactions. + <application>pg_dump</application> takes advantage of the new + MVCC features to give a consistant database dump/backup while + the database stays online and available for queries. </para> </listitem> </varlistentry> @@ -84,7 +92,7 @@ <para> We now have CASE, INTERSECT, and EXCEPT statement support. We have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, - SELECT ... FOR UPDATE, and an improved LOCK command. + SELECT ... FOR UPDATE, and an improved LOCK TABLE command. </para> </listitem> </varlistentry> @@ -184,7 +192,7 @@ <command>SELECT</command> it doesn't mean that this row really exists at the time it is returned (i.e. sometime after the statement or transaction began) nor that the row is protected from deletion or - updation by concurrent transactions before the current transaction does + update by concurrent transactions before the current transaction does a commit or rollback. </para> diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml index 72043575f38..e9c3467638a 100644 --- a/doc/src/sgml/syntax.sgml +++ b/doc/src/sgml/syntax.sgml @@ -1,4 +1,4 @@ - <chapter> + <chapter id="syntax"> <title>SQL Syntax</title> <abstract> |