From: Brian Fehrle <brianf@consistentstate.com>
To: pgsql-admin@postgresql.org
Cc: Kevin Kempter <kevink@consistentstate.com>
Subject: archive_timeout behavior (8.4.6)
Date: Fri, 22 Apr 2011 18:23:22 -0600
Message-ID: <4DB21BFA.4030800@consistentstate.com> (raw)
Hi all,
We thought we were having issues with our warm standby (postgres
8.4.6), but think we figured it out, however I'd like someone to confirm
what we think is true.
If a cluster has zero activity whatsoever, but we have archive_timeout
set (say to 60 seconds), will it create a WAL file anyways, or knowing
there was zero activity does it skip it? We turned it on (temporarily)
to force WAL files to go to a newly set up warm standby so we could
verify that we have the whole end-to-end process correct, but we didn't
have any WAL files transfer to the warm standby. After some trouble
shooting, we notice that we do get a WAL file shortly after we insert a
single row into a table.
The confusion is probably because I remember this same scenario on older
versions of 8.4, and watching it generate wal files even with no activity.
So long story short, if a cluster has zero activity, and archive_timeout
is not set to 0, when it reaches that timeout should it generate a file,
or just skip because it would be 100% empty?
Thanks in advance,
Brian F
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: brianf@consistentstate.com, kevink@consistentstate.com
Subject: Re: archive_timeout behavior (8.4.6)
In-Reply-To: <4DB21BFA.4030800@consistentstate.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox