On Thu, Jun 24, 2010 at 10:13 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Simon Riggs <si...@2ndquadrant.com> writes: >> On Wed, 2010-06-23 at 21:54 +0000, Robert Haas wrote: >>> This adds four additional connection parameters to libpq: keepalives, >>> keepalives_idle, keepalives_count, and keepalives_interval. >>> keepalives default to on, per discussion, but can be turned off by >>> specifying keepalives=0. The remaining parameters, where supported, >>> can be used to adjust how often keepalives are sent and how many >>> can be lost before the connection is broken. > >> There isn't any need at at all for this. We can already add options on >> the libpq connection line. > >> options = '-o tcp_keepalives_idle=X >> tcp_keepalives_interval=Y >> tcp_keepalives_count=Z' > > Huh? The above is 100% fanciful; there was no code in libpq or anywhere > else that would have processed such a thing.
You can do this: psql "host=127.0.0.1 options='-c tcp_keepalives_idle=1'" ...but it doesn't do the same thing as this patch. It lets you set the TCP keepalive parameters on the server side, whereas what this patch does is let you set them on the client side. Only setting them on the client side will allow the client to notice when the server has gone away. There is still an open question in my mind as to whether this is really an adequate solution to the walrecevier problem, but as you say, if it turns out not to be, it's got other value. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers