On Fri, Dec 16, 2011 at 10:01 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> To provide some form of keepalive on quiet systems the
> archive_keepalive_command provides a generic hook to implement
> keepalives. This is implemented as a separate command to avoid storing
> keepalive messages in the archive, or at least allow overwrites using
> a single filename like "keepalive".
This may be stupid of me, but I don't see the point of this. If you
want keepalives, why use log shipping rather than SR? Implementing a
really-high-latency method of passing protocol messages through the
archive seems like a complex solution to a non-problem (but, like I
say, I may be missing something).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company