aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-06-28 12:30:16 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-06-28 12:30:16 -0400
commit99255d73c07c89b69be028a1a7b8027a78befed4 (patch)
treeb3729d0e330a55abe5df617ca6788d82773696c1 /src/backend/executor/nodeModifyTable.c
parent4500edc7e9cf771bf8960d1f3f620917871bdb6f (diff)
downloadpostgresql-99255d73c07c89b69be028a1a7b8027a78befed4.tar.gz
postgresql-99255d73c07c89b69be028a1a7b8027a78befed4.zip
Second try at fixing tcp_keepalives_idle option on Solaris.
Buildfarm evidence shows that TCP_KEEPALIVE_THRESHOLD doesn't exist after all on Solaris < 11. This means we need to take positive action to prevent the TCP_KEEPALIVE code path from being taken on that platform. I've chosen to limit it with "&& defined(__darwin__)", since it's unclear that anyone else would follow Apple's precedent of spelling the symbol that way. Also, follow a suggestion from Michael Paquier of eliminating code duplication by defining a couple of intermediate symbols for the socket option. In passing, make some effort to reduce the number of translatable messages by replacing "setsockopt(foo) failed" with "setsockopt(%s) failed", etc, throughout the affected files. And update relevant documentation so that it doesn't claim to provide an exhaustive list of the possible socket option names. Like the previous commit (f0256c774), back-patch to all supported branches. Discussion: https://postgr.es/m/20170627163757.25161.528@wrigleys.postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions