rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change wording so that you don't need to understand that wal_levels 

form a hierarchy. Per Simon's suggestion.
This commit is contained in:
Heikki Linnakangas 2010-05-03 10:31:29 +00:00
parent 1b6c7b1c0b
commit c0de88c415
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/config.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.275 2010/05/03 09:14:17 heikki Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.276 2010/05/03 10:31:29 heikki Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@ -1375,7 +1375,8 @@ SET ENABLE_SEQSCAN TO OFF;
safely skipped, which can make those operations much faster (see
<xref linkend="populate-pitr">). But minimal WAL does not contain
enough information to reconstruct the data from a base backup and the
WAL logs, so at least <literal>archive</> level must be used to enable
WAL logs, so either <literal>archive</> or <literal>hot_standby</>
level must be used to enable
WAL archiving (<xref linkend="guc-archive-mode">) and streaming
replication.
</para>