| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cascaded standby message |
| Date: | 2011-09-07 01:44:27 |
| Message-ID: | CAHGQGwHxLq6_-t_CoiOJamgPiLZub2W=4tFt5B1BPUgAWizhYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 7, 2011 at 5:22 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Fujii - the original goal here was to avoid having a unexplained
> disconnection in the logs. The only way to do this cleanly is to have
> a disconnection reason passed to the walsender, rather than just a
> blind signal. Looks like we need to multiplex or other mechanism.
That's an idea. But what about the patch that I proposed before?
http://archives.postgresql.org/pgsql-hackers/2011-08/msg00816.php
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-09-07 02:11:54 | Re: postgresql.conf archive_command example |
| Previous Message | Bruce Momjian | 2011-09-07 01:43:15 | Re: Back branch update releases this week; beta postponed |