Prev: EOL for 7.4 and 8.0
Next: [HACKERS] EOL for 7.4 and 8.0
From: Simon Riggs on 24 Jun 2010 13:38
On Thu, 2010-06-24 at 11:15 -0400, Tom Lane wrote:
> Florian Pflug <fgp(a)phlo.org> writes:
> > On Jun 24, 2010, at 16:45 , Robert Haas wrote:
> >> I think the existing names are fine - people should understand that
> >> "options" means "server-side options" and that anything else is a
> >> client-side option. However, if there's a strong consensus the other
> >> way and someone feels like working up a patch, that's fine too.
>
> > I'd volunteer to create the patch if people think renaming the libpq options is a good idea.
>
> I'm with Robert: the names are fine as-is. We've not had complaints
> about the libpq SSL parameters being confusingly like server-side SSL
> parameters, for instance.
>
> It might be a good idea to add a sentence to the documentation, though,
> just pointing out that these control client-side keepalive probes rather
> than server-side.

Yes please. I was confused; I think others will be also.

--
Simon Riggs www.2ndQuadrant.com



--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 24 Jun 2010 13:40
On Thu, 2010-06-24 at 10:30 -0400, Robert Haas wrote:

> 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.

Thank you for explaining. Now I understand.

It sort of begs the question: why need they be different?

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: EOL for 7.4 and 8.0
Next: [HACKERS] EOL for 7.4 and 8.0