Ray Stell wrote:
> On Wed, Jan 26, 2011 at 02:22:41PM -0800, Dan Birken wrote:
> > > Can you give some concrete suggestions on what needs to be added? The
> > > current documentation is here:
> > >
> > > http://developer.postgresql.org/pgdocs/postgres/index.html
>
>
> I had some difficulty getting the keepalives syntax in recovery.conf.
>
>
> http://developer.postgresql.org/pgdocs/postgres/warm-standby.html#STREAMING-REPLICATION
>
> might stand an example. When you click on the link there it takes you here:
>
>
> http://developer.postgresql.org/pgdocs/postgres/runtime-config-connection.html#GUC-TCP-KEEPALIVES-IDLE
>
> which doesn't help to much. Somewhere I found a comment that did it this way:
>
> primary_conninfo = 'host=test user=fred keepalives_idle= 60 '
>
> The example I found for this in "PostgreSQL 9 Admin Cookbook" didn't
> fly: primary_conninfo = '....options="-c tcp_keepalives_idle= 60" ...'
> I didn't check the erratta. Just sayin....
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.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
