| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: archive_keepalive_command |
| Date: | 2011-12-19 13:17:44 |
| Message-ID: | CA+TgmoY8VTqTJc1o8rqUMrGvcoR1B8KYFy5LL922B5B0TREKkA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 16, 2011 at 10:01 AM, Simon Riggs <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-12-19 14:06:54 | Re: archive_keepalive_command |
| Previous Message | Robert Haas | 2011-12-19 13:13:04 | Re: Review: Non-inheritable check constraints |