Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Looking at the archive_timeout documentation and
> CheckArchiveTimeout(), it appears we force a new xlog file and
> archive it even if no activity has been recorded in the xlog file.
> Is this correct? Should we document this or fix it so only xlog
> files with contents are archived?
Er, you can probably blame me for that. Tom was going to fix it and
I pointed out that it would break our monitoring of our warm standby
processes. We have a one hour maximum and send alerts if we've gone
75 minutes or more without receiving a WAL file from one of our
databases. Of course, if we had a nicer way to know that we were
up-to-date with our WAL file copies, we wouldn't need this; but
right now there aren't a lot of options for monitoring these things.
In response to
pgsql-hackers by date
|Next:||From: Tim Bunce||Date: 2010-01-14 16:07:16|
|Subject: Miscellaneous changes to plperl [PATCH]|
|Previous:||From: Dimitri Fontaine||Date: 2010-01-14 16:06:36|
|Subject: Re: Streaming replication, retrying from archive|