From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [REVIEW] pg_last_xact_insert_timestamp |
Date: | 2011-12-12 14:47:34 |
Message-ID: | CA+TgmoYkVsC-WrEF7H7AZgC7uWr_5Oki8DkY5EjDQE7JS5PspA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 12, 2011 at 9:24 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Mon, Dec 12, 2011 at 1:45 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> It also strikes me that anything
>> that is based on augmenting the walsender/walreceiver protocol leaves
>> anyone who is using WAL shipping out in the cold. I'm not clear from
>> the comments you or Simon have made how important you think that use
>> case still is.
>
> archive_timeout > 0 works just fine at generating files even when
> quiet, or if it does not, it is a bug.
>
> So I don't understand your comments, please explain.
If the standby has restore_command set but not primary_conninfo, then
it will never make a direct connection to the master. So anything
that's based on extending that protocol won't get used in that case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-12-12 14:51:10 | Re: [REVIEW] pg_last_xact_insert_timestamp |
Previous Message | Simon Riggs | 2011-12-12 14:24:41 | Re: [REVIEW] pg_last_xact_insert_timestamp |