| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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 14:28:26 |
| Message-ID: | 1298039306.2226.4834.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Fri, 2011-02-18 at 07:11 -0500, Robert Haas wrote:
> 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.
Thanks for the observation.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-02-18 15:09:15 | pgsql: Make a hard state change from catchup to streaming mode. |
| Previous Message | Robert Haas | 2011-02-18 12:11:01 | Re: [COMMITTERS] pgsql: Separate messages for standby replies and hot standby feedback. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-18 14:55:04 | Re: About the performance of startup after dropping many tables |
| Previous Message | Robert Haas | 2011-02-18 14:09:13 | Re: Assertion failure on UNLOGGED VIEW and SEQUENCE |