From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | wal_level and continuous archiving documentation |
Date: | 2010-05-13 16:42:18 |
Message-ID: | 4bec2bed.011c640a.07e7.3588@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I was reading through
http://www.postgresql.org/docs/9.0/static/continuous-archiving.html and
noticed that wal_level isn't mentioned where I'd expect it to be.
Specifically, there's a paragraph that starts, "To enable WAL archiving, set
the archive_mode configuration parameter to on, and specify the shell command
to use in the archive_command configuration parameter." There follows a long
discussion of archive_command, but no further discussion of other
configuration settings for several paragraphs, suggesting that those two
configuration changes are the only ones required to end up with a useful
archive. However, further on, it discusses wal_level:
"When wal_level is minimal some SQL commands are optimized to avoid WAL
logging, as described in Section 14.4.7. If archiving or streaming
replication were turned on during execution of one of these statements,
WAL would not contain enough information for archive recovery."
ISTM wal_archive should make an appearance where the docs bring up
archive_mode and archive_command, to say "wal_level must be set to 'archive'
or 'hot_standby'", so all required configuration changes are mentioned close
together.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-05-13 16:51:30 | Re: [HACKERS] Retiring from the PostgreSQL core team |
Previous Message | Tom Lane | 2010-05-13 15:37:30 | Re: pg_upgrade code questions |