aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-10-18 12:56:43 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-10-18 12:56:43 -0400
commitd5a9a661fcd2f5db037274157f931863a52004fd (patch)
treeb55f42c2a9e48a77b4bd6ace0fd2ec8e19603e85 /src/backend/executor/nodeModifyTable.c
parent929c69aa1970b3ae30bbb5a159b9dc530ec34d5c (diff)
downloadpostgresql-d5a9a661fcd2f5db037274157f931863a52004fd.tar.gz
postgresql-d5a9a661fcd2f5db037274157f931863a52004fd.zip
Update the Winsock API version requested by libpq.
According to Microsoft's documentation, 2.2 has been the current version since Windows 98 or so. Moreover, that's what the Postgres backend has been requesting since 2004 (cf commit 4cdf51e64). So there seems no reason for libpq to keep asking for 1.1. Bring thread_test along, too, so that we're uniformly asking for 2.2 in all our WSAStartup calls. It's not clear whether there's any point in back-patching this, so for now I didn't. Discussion: https://postgr.es/m/132799.1602960277@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions