| From: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Dan Birken <dan(at)thumbtack(dot)com>, Ben Carbery <ben(dot)carbery(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Understanding PG9.0 streaming replication feature |
| Date: | 2011-01-27 02:34:18 |
| Message-ID: | 20110127023418.GC31642@cns.vt.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 26, 2011 at 09:18:01PM -0500, Bruce Momjian wrote:
>
> Uh, the sentence is:
>
> On systems that support the keepalive socket option, setting
> tcp_keepalives_idle, tcp_keepalives_interval and tcp_keepalives_count
> helps the primary promptly notice a broken connection.
>
> I believe there they are talking about setting those values in the
> master/primary so you see the slave has disconnected --- this is not
> related to setting in the connection string, I think.
Yep. Simon shows it the other way in his book:
"If you want a Standby to notice that the connection to the Master has
dropped, you need to set the keepalives in the primary_conninfo in the
recovery.conf"
That works, also.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-01-27 07:45:52 | Re: Adding ddl audit trigger |
| Previous Message | Bruce Momjian | 2011-01-27 02:18:01 | Re: Understanding PG9.0 streaming replication feature |