| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Oliver Jowett" <oliver(at)opencloud(dot)com> |
| Cc: | <pgsql-patches(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL (was Re: [HACKERS] Feature freeze date for 8.1) |
| Date: | 2005-09-08 19:33:27 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD2C6@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 pgsql-patches |
> Here's a patch that adds four new GUCs:
>
> tcp_keepalives (defaults to on, controls SO_KEEPALIVE)
> tcp_keepalives_idle (controls TCP_KEEPIDLE)
> tcp_keepalives_interval (controls TCP_KEEPINTVL)
> tcp_keepalives_count (controls TCP_KEEPCNT)
I just tested this on my windows XP machine running rc1. A default
configuration reports zeros for the tcp values in a 'show all'. More
significantly, if you change a tcp parameter from the default, the
server rejects connections without a relevant error message :(.
I did some research and the only way to control these parameters is to
adjust the system registry plus a reboot. (somebody correct me here).
If that is the case IMO it makes the most sense to have the server fail
to start if the default parameters are changed.
Even better would be a stronger test to make sure o/s supports this
feature.
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-09-08 23:09:50 | Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL |
| Previous Message | Dave Page | 2005-09-08 13:46:07 | pgInstaller 8.1 dev build |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-09-08 22:14:54 | FAQ numbering fix |
| Previous Message | Martijn van Oosterhout | 2005-09-08 17:43:33 | Re: For review: Initial support for COLLATE |