WAL log level compatibility
Hi everyone,
Are 'wal_level = archive' vs 'wal_level = hot_standby' ok to mix? For
example, let's say I had a PostgreSQL database running and creating WAL
logs in the archive level. Then we switch to the hot standby level to
support a hot standby, then go back to the archive level, all while
uploading WAL logs to the same location. Would PostgreSQL be able to do
PITR over this entire span of time?
Thanks!
-Andy
On Thu, Aug 21, 2014 at 11:26:39PM +0000, Andy Lau wrote:
Hi everyone,
Are 'wal_level = archive' vs 'wal_level = hot_standby' ok to mix? For example,
let's say I had a PostgreSQL database running and creating WAL logs in the
archive level. Then we switch to the hot standby level to support a hot
standby, then go back to the archive level, all while uploading WAL logs to the
same location. Would PostgreSQL be able to do PITR over this entire span of
time?
Yes, PITR needs any wal_level other than "minimal".
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general