David Steele 5c6fb88bef TCP keep-alive options are configurable. ... Prior to 2.25 the individual TCP keep-alive options were not being configured due to a missing header. In 2.25 they were being configured incorrectly due to a disconnect between the timeout specified in ms and what was expected by the TCP options, i.e. seconds. Instead make the TCP keep-alive options directly configurable, with correct units and better testing. Keep-alive is enabled by default (though it can be defaulted to the system setting instead) and the rest of the options are not set by default. This is in line with what PostgreSQL does, though PostgreSQL does not allow keep-alive to be defaulted. Also move configuration of TCP options before connect() as PostgreSQL does.		2020-03-31 18:13:11 -04:00
..
Build.pm	Move pgBackRest::Version module to pgBackRestDoc::ProjectInfo.	2020-03-10 17:57:02 -04:00
BuildDefine.pm	Move pgBackRest::Version module to pgBackRestDoc::ProjectInfo.	2020-03-10 17:57:02 -04:00
BuildParse.pm	Move pgBackRest::Version module to pgBackRestDoc::ProjectInfo.	2020-03-10 17:57:02 -04:00
Data.pm	TCP keep-alive options are configurable.	2020-03-31 18:13:11 -04:00