| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Separate messages for standby replies and hot standby feedback. |
| Date: | 2011-02-18 12:11:01 |
| Message-ID: | AANLkTikoCWqhUnoCsOXmUZUcK0WcWLJMfg8=9HmuBR80@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Fri, Feb 18, 2011 at 6:34 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Separate messages for standby replies and hot standby feedback.
> Allow messages to be sent at different times, and greatly reduce
> the frequency of hot standby feedback. Refactor to allow additional
> message types.
You could refactor this some more to avoid calling
GetCurrentTimestamp() and TimestampDifferenceExceeds() twice each, but
I'm not sure whether it's worth it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-02-18 14:28:26 | Re: [COMMITTERS] pgsql: Separate messages for standby replies and hot standby feedback. |
| Previous Message | Simon Riggs | 2011-02-18 11:34:05 | pgsql: Separate messages for standby replies and hot standby feedback. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-18 12:37:46 | Re: About the performance of startup after dropping many tables |
| Previous Message | Simon Riggs | 2011-02-18 11:50:58 | Server Name |